Entry Point Audit
Use when adding any cross-cutting change - a new gate, limit, permission check, or rule that must apply everywhere.
Install
$ agentstack add skill-fergius-engineering-instincts-entry-point-audit ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-fergius-engineering-instincts-entry-point-audit) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
The rule
When a change has to hold everywhere, the bug is the path you forgot. Before you add it to the handler in front of you, search the whole codebase for every entry point that reaches the same action, and apply it to all of them.
Fires when
Adding a limit or quota, an auth or permission check, a feature flag or gate, input validation, or logging that must always fire for some action.
How to apply
Grep the codebase for the action itself, not just the caller you're looking at: the function, the event, the command. Assume two or three entry points exist, not one. Apply the change to every one of them. Then search again to confirm none are left.
Worked example
You add a rate limit to the REST endpoint that sends invites. Shipped. Users still spam invites, because the same send-invite function is also called from a CLI command and a nightly cron job, and neither is rate-limited.
The limit had to live at every entry point, or below all of them. Not just the HTTP door you happened to be standing at.
Red flags
| Thought | Reality | |---|---| | "I'll add it to this handler" | Which handler? Find all of them first. | | "There's only one place this happens" | Assume three until you've checked. | | "It works from the UI" | The UI is one door. Count the others. |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Fergius-Engineering
- Source: Fergius-Engineering/instincts
- License: MIT
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.