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/tranhieutt/software_development_department/api-designnpx skills add tranhieutt/software_development_department --skill api-designgit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tranhieutt/software_development_department/api-design)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/api-design"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/api-design.svg" alt="Measured on agentmods" height="20"></a>What 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.00053 | $0.00920 |
| Opus 5 | $0.00026 | $0.00460 |
| Sonnet 5 | $0.00011 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
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 4d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When this skill is invoked:
-
Read the target API spec or route files in full.
For API design in an existing domain, SHOULD also inspect
docs/technical/API.md, relateddesign/specs/*, relateddesign/contracts/*if present, and recent relevant ledger entries via/trace-history. This is advisory unless the change is an ADR, coordination-rule change, high-risk retry, or protocol removal. -
Identify the API type (REST, GraphQL, WebSocket) and apply appropriate standards.
-
Evaluate REST design quality (if REST):
- Resources use nouns, not verbs (
/users, not/getUsers) - Correct HTTP methods (GET=read, POST=create, PUT/PATCH=update, DELETE=remove)
- Consistent plural resource naming (
/users,/orders) - Nested resources have max 2-3 levels of depth
- Query parameters used for filtering, sorting, pagination (not in path)
- Resources use nouns, not verbs (
-
Evaluate request/response schemas:
- All inputs are validated and typed
- Responses are consistent in structure (envelope format if used)
- Pagination is consistent (cursor or page-based, not mixed)
- Timestamps in ISO 8601 (UTC)
- Money values in smallest currency unit (cents), not floats
-
Evaluate authentication & authorization:
- Every endpoint has explicit auth requirement documented
- Authorization is checked server-side, not just on the client
- Sensitive data not leaked in error messages
-
Evaluate error responses:
- Consistent error format (RFC 7807 Problem Details recommended)
- HTTP status codes used correctly (400 for client errors, 500 for server)
- Error messages are user-safe (no stack traces, SQL errors)
-
Evaluate versioning & backward compatibility:
- Breaking changes require a version bump
- Deprecation policy documented
- Clients can negotiate API version
-
Output the review:
## API Design Review: [API/Endpoint Name]
### REST Design: [CLEAN / ISSUES FOUND]
[List specific issues with examples]
### Schema Quality: [CLEAN / ISSUES FOUND]
[List schema inconsistencies or problems]
### Auth & Security: [SECURE / ISSUES FOUND]
[List authentication and authorization issues]
### Error Handling: [CONSISTENT / ISSUES FOUND]
[List error response problems]
### Versioning: [HANDLED / UNADDRESSED]
[Notes on breaking change risk]
### Positive Observations
[What is well-designed]
### Required Changes
[Must-fix items before shipping]
### Suggestions
[Nice-to-have improvements]
### Verdict: [APPROVED / APPROVED WITH SUGGESTIONS / CHANGES REQUIRED]
Protocol
- Question: Auto-starts from argument (path to API spec or route files); no clarification needed
- Options: Skip — single review path
- Decision: Skip — verdict is advisory
- Draft: Full review report shown in conversation only
- Approval: Skip — read-only; no files written
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.
- 4d ago First seen · 101 lines · 53 tokens per session scan A 38a7a3d289bb
api-design is a skill published in the GitHub repository tranhieutt/software_development_department (71 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 920 once invoked, about $0.0003 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-30.
Other skills, from other repositories
blockchain-developer
Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3 apps, DeFi protocols, or blockchain infrastructure.
contract-decode
EVM contract error and calldata decoder. Use when: user pastes hex revert data, calldata, function selector, or mentions custom error, execution reverted, 4byte, decode. Input contains 0x + 8+ hex chars.
portfolio
Portfolio system knowledge base. Use when: position queries, routing strategy questions, provider integration. Not for: general code exploration (use code-explore), code review (use codex-code-review). Output: domain-specific analysis + recommendations.
smart-contracts
Skill "smart-contracts" from DongDuong2001/pudo-code-system, covering web3 & smart contracts pudo checklist, 1. plan (architecture & strategy), 2. understand (context & auditing), 3. develop (implementation) and 4. optimize (performance & review).
brainstorming
You MUST use this before any creative work (features, products, content, strategy, systems, or behavior changes). Start by classifying what we’re brainstorming, then run thorough one-question-at-a-time discovery, propose 2–3 approaches, and converge on a validated plan/spec.
email-sequence
Design and draft lifecycle email sequences such as welcome, onboarding, nurture, re-engagement, and upgrade flows. Use when defining triggers, sequence maps, email copy, and performance metrics. Produce file-first outputs under scripts/marketing/ / and align with product marketing context.