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/ambystechcom/ambykit/amby-specifynpx 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.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.00023 | $0.00499 |
| Opus 5 | $0.00012 | $0.00249 |
| Sonnet 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 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.
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.
- 4d 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 8d ago), licensed MIT. It adds 23 tokens to every session and 499 once invoked, about $0.0001 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
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
moai-foundation-core
Provides MoAI-ADK foundational principles including TRUST 5 quality framework, SPEC-First DDD methodology, delegation patterns, progressive disclosure, agent catalog reference, and token budget management (absorbed from moai-foundation-context). Use when referencing TRUST 5 gates, SPEC workflow, or context window…
hns-lsel-applier
Local Self-Evolution Loop (LSEL) APPLY engine — the playback-only consumer of approved decision.json records that drives .moai/hooks/lsel-apply.sh for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001 M3). Reads an approved decision.json, validates the target against the frozen allowlist…
moai-domain-database
Database specialist covering PostgreSQL, MongoDB, Redis, Oracle, and cloud database platforms (Neon, Supabase, Firestore). Use for schema design, query optimization, indexing strategies, data modeling, or cloud database selection. Cloud vendor guide absorbed from moai-platform-database-cloud.
moai-workflow-ddd
Domain-Driven Development workflow specialist using ANALYZE-PRESERVE-IMPROVE cycle for behavior-preserving code transformation. Use when refactoring legacy code or reducing technical debt safely.
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…