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 ambystechcom/AmbyKit --skill amby-specifygit clone --depth 1 https://github.com/ambystechcom/AmbyKitWrote 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/ambystechcom/ambykit/amby-specify)<a href="https://agentmods.dev/skills/ambystechcom/ambykit/amby-specify"><img src="https://agentmods.dev/badge/skills/ambystechcom/ambykit/amby-specify/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ambystechcom/ambykit/amby-specify"><img src="https://agentmods.dev/badge/skills/ambystechcom/ambykit/amby-specify.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00499 |
| Opus 5.5 | $0.00009 | $0.00200 |
| Sonnet 5.5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
amby-specify 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 1mo 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.
What it actually says
Act as the Product Manager in @.amby/roles/pm.md and say so in your first line. If the user's request that followed this skill invocation contains --as <id>, use @.amby/roles/<id>.md instead; if that file is missing, stop and list the files in .amby/roles/.
Write a specification for: the user's request that followed this skill invocation
Context: read @.amby/constitution.md and the structure of @.amby/templates/spec.md only. Do not
read other specs.
- Create the feature dir
specs/NNN-slug/(next number, kebab-slug from the title) and writespec.mdfollowing@.amby/templates/spec.md. - Define user stories (
US-#): role / capability / benefit, a priority (P1/P2/P3), why that priority, an independent-test statement, anddepends-on/blocked-byif any. Setstatus: draft. - Write acceptance criteria in Given/When/Then per story.
- Write functional requirements (
FR-###) in EARS notation (SHALL / WHEN / WHILE / IF-THEN / WHERE). Each must be testable. - Write measurable, tech-agnostic success criteria (
SC-###). - Capture WHAT/WHY only — no technology choices. Flag every unknown inline as
[NEEDS CLARIFICATION: …]instead of guessing. - If
.amby/config.jsonhas"worktrees": trueand this is a git repo, runambykit worktree NNN-slug(the only command to run) and tell the user to continue in.worktrees/NNN-slug/. Otherwise skip this step (say why if isolation was enabled but git is absent).
Keep it tight. Reference the constitution by principle number where relevant; don't restate it.
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.
- 1mo ago First seen · 29 lines · 23 tokens per session scan A cb790fdd9b0b
amby-specify is a skill published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 499 once invoked, about $0.0001 per session on Opus 5.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
importing-a-codebase
Use when asked to create the initial spec graph for an existing codebase that has source code but no specs. Normally reached via setting-up-a-project.
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.