Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/m-binimran/dev-pack/api-designnpx skills add m-binimran/dev-pack --skill api-designgit clone --depth 1 https://github.com/m-binimran/dev-packWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00040 | $0.00421 |
| Opus 5 | $0.00020 | $0.00211 |
| Sonnet 5 | $0.00008 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
api-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
api-design
The server boundary between UI and database. Validate everything; never trust the caller.
Choose the right tool
- Server Action — form submits / mutations from your own UI. Co-located, type-safe, no manual fetch.
- Route Handler (
app/api/.../route.ts) — webhooks, third-party callers, public/REST endpoints, file streams.
Every endpoint
- Validate input with Zod at the top. Reject early with
400+ a useful message. Re-validate even if the client already did. - Authenticate + authorize: get the user (server), check they may do this. RLS is the backstop, not the only gate for sensitive actions.
- Correct status codes: 200/201 success, 400 bad input, 401 unauthenticated, 403 forbidden, 404 missing, 409 conflict, 429 rate-limited, 500 only for true server faults.
- Handle errors explicitly. Catch, log server-side, return a safe message — never leak stack traces or DB errors to the client.
- Rate-limit public/mutating endpoints (e.g. Upstash). Idempotency keys for anything chargeable.
- Shape responses consistently (
{ data }/{ error }); don't return raw DB rows with internal columns.
Output
- The handler/action, the Zod schema, the auth check, and the status codes it returns.
- Note what's validated, what's rate-limited, and what an attacker could try.
Guardrails
- No unvalidated input reaching the DB or filesystem.
- No secrets or internal error details in responses.
- Mutations are POST/PUT/PATCH/DELETE, not GET.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 34 lines · 40 tokens per session scan A 57c4e0ef8433
api-design is a skill published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 421 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
investigate-issue
Investigate a GitHub issue by fetching details, analyzing the codebase, researching documentation, and presenting an actionable implementation plan with test guidance. Use when asked to investigate, analyze, triage, or plan work for a GitHub issue. Invoked with /investigate-issue or /investigate-issue (prompts for ID).
resolve-pr-comments-stack
Resolve unresolved PR review comments across an entire Graphite (gt) stack of many PRs, bottom-up, in one working directory. Use when asked to "go through this stack and resolve comments", "clean up review comments across the whole stack", or given a list/range of PR numbers that form (or partially form) a gt stack.…
resolve-pr-comments
Skill "resolve-pr-comments" from maximhq/bifrost, covering resolve pr comments, usage, workflow overview, step 1: detect repository and step 2: fetch unresolved comments (graphql).
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
trulens-blocking-guardrails
Configure and use feedback functions as runtime blocking guardrails.
review-pr
Reviews a PR or diff with multi-angle finders and adversarial verification, then reports a findings table, a merge/no-merge recommendation, required followups, and offers to create a follow-up PR. Use when the user types /review-pr [PR# | branch | path].