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 skills add marcoguillermaz/Tierward --skill api-designgit clone --depth 1 https://github.com/marcoguillermaz/TierwardWrote 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/marcoguillermaz/tierward/api-design)<a href="https://agentmods.dev/skills/marcoguillermaz/tierward/api-design"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/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.1 | $0.00000 | $0.03958 |
| Opus 5 | $0.00000 | $0.01979 |
| Sonnet 5 | $0.00000 | $0.00792 |
| Haiku 4.5 | $0.00000 | $0.00396 |
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 8d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope: endpoint naming, HTTP verbs, resource modeling, response shapes, error codes, field naming, filtering/sorting conventions, pagination, validation, auth/authz boundary clarity.
Out of scope: auth implementation → /security-audit | performance → /perf-audit | DB schema → /skill-db.
Default mode: audit (no code changes). Modes: audit | remediation (propose plan, no changes) | apply (make focused fixes).
All audit findings are persisted to docs/refactoring-backlog.md via the backlog write-once protocol (.claude/rules/backlog-protocol.md).
Configuration
| Placeholder | Description | Example |
|---|---|---|
[SITEMAP_OR_ROUTE_LIST] |
File listing all API routes with method, path, roles, and grouping | docs/sitemap.md, docs/routes.md |
Unfilled behavior: if [SITEMAP_OR_ROUTE_LIST] is not filled, the skill discovers routes by scanning the project's route handler directories. Announce the discovered routes before proceeding.
Status code reference (source: MDN + RFC 9457)
- 400 - malformed request: bad JSON, schema validation failure, missing required field
- 401 - not authenticated (no valid session)
- 403 - authenticated but lacks permission
- 404 - resource not found
- 409 - valid request conflicts with current server state (e.g., approving an already-approved record, duplicate unique value)
- 422 - semantically invalid data that passes schema validation but violates a business rule
- 500 - unexpected server error (no internal details in response)
Step 0 - Target and mode resolution
Parse $ARGUMENTS for target: and mode: tokens.
Target:
| Pattern | Meaning |
|---|---|
target:section:export |
Only export/bulk routes (example) |
target:section:<other> |
Resolve by reading [SITEMAP_OR_ROUTE_LIST] API routes section, filtering for routes whose path or group label contains <other>. Announce the resolved route list before proceeding. |
| No argument | Full audit - ALL API routes across the entire codebase. Maximum depth. |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 250 lines · 0 tokens per session scan A 837140d75ebb
api-design is a skill published in the GitHub repository marcoguillermaz/Tierward (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,958 tokens. 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
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a…
spring-boot-patterns
Spring Boot best practices and patterns. Use when creating controllers, services or repositories, or when the user asks about Spring Boot layering, wiring, configuration or exception handling. For JPA and Hibernate behaviour, use jpa-patterns instead.
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
harness-engineering
Use when the user asks to improve, fix, or build their repository's AI harness — AGENTS.md, rules, skills, commands, hooks, guardrails, CI sensors — or to act on harness-score audit findings and raise their maturity level.