— No reviews yet
0 installs
15 views
0.0% view→install
Install
$ agentstack add skill-floomhq-moto-bouncer Open-source listing — not yet scanned by AgentStack. Follow the source repository for install instructions.
Security review
⚠ Flagged1 finding(s); flagged for manual review. · v0.1.0 How review works →
- • Prompt-injection patterns
- • Secret / credential exfiltration
- • Dangerous shell & filesystem operations
- • Untrusted network calls
- • Known-malicious package signatures
- high Destructive filesystem operation.
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Are you the author of Bouncer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claimAbout
Bouncer: Pre-flight Risk Check
Before proceeding with any significant action, run this check. The bouncer's job is to catch bad ideas before they become problems.
The Three Questions
- Is this reversible?
- If yes: proceed carefully
- If no: require explicit confirmation and atomic commit first
- Is this the right time?
- Are there uncommitted changes that should be committed first?
- Are there tests that should pass first?
- Is there a blocking issue that should be resolved first?
- Is the scope correct?
- Is the proposed change proportional to the stated problem?
- Are there unintended side effects?
- Is this solving the root cause or a symptom?
Risk Categories
Green (proceed)
- Additive changes (new files, new functions)
- Changes to development/test environments
- Reversible config changes
- Changes with good test coverage
Yellow (proceed with caution)
- Modifying existing logic
- Database schema changes with migration
- Changes affecting multiple consumers
- Production config changes
Red (require explicit confirmation)
- Deleting data or files
- Breaking API changes
- Production deployments without test pass
- Changes to auth or security logic
- Any
rm -rf,DROP TABLE, or irreversible operations
Checklist
Before any significant change:
- [ ] Understand what is being changed and why
- [ ] Identify all files/systems affected (grep for callers)
- [ ] Confirm tests exist or will be written
- [ ] Confirm the change is reversible OR have a rollback plan
- [ ] For production changes: confirm staging was tested first
Response Format
When invoked, output:
BOUNCER CHECK
Risk level: [GREEN / YELLOW / RED]
Reversible: [YES / NO / PARTIAL]
Preconditions met: [YES / NO - missing: ...]
Recommendation: [PROCEED / PROCEED WITH CAUTION / STOP AND CONFIRM]
Reason: [brief explanation]
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: floomhq
- Source: floomhq/moto
- License: MIT
- Homepage: https://github.com/floomhq/moto#readme
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.