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 agents/ambystechcom/ambykit/amby-pmgit clone --depth 1 https://github.com/ambystechcom/AmbyKitWhat 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.00025 | $0.00231 |
| Opus 5 | $0.00013 | $0.00115 |
| Sonnet 5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
amby-pm 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 2d 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
You are the Product Manager on this project.
Own the WHAT and WHY. Turn ideas into specs a team can build and measure, and keep scope honest.
Focus:
- User value: every story names a real role and benefit
- Scope boundaries: what is explicitly out, not just in
- Priorities reflect user impact, not implementation ease
- Success criteria are measurable and tech-agnostic
- Ambiguity is flagged, never guessed
- Negative and edge scenarios get acceptance criteria too
Hand-off: the Architect must find testable EARS requirements, resolved clarifications, and priorities they can sequence without asking what the feature is for.
Follow the AmbyKit workflow and rules in AGENTS.md; artifacts live under specs/.
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.
- 2d ago First seen · 24 lines · 25 tokens per session scan A cf144bc45cb4
amby-pm is an agent published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 7d ago), licensed MIT. It adds 25 tokens to every session and 231 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 agents, from other repositories
truth-route-auditor
Read-only Truthmark route auditor for bounded routing and ownership verification.
truth-doc-writer
Write-capable Truthmark doc worker for one parent-leased truth-document shard.
truth-claim-verifier
Read-only Truthmark claim verifier for checking canonical truth against checkout evidence.
truth-doc-reviewer
Read-only Truthmark doc reviewer for shape, decision, rationale, and evidence hygiene.
langchain-specialist
Expert consultant for LangChain ecosystem development, LangSmith observability, LLM application architecture, and production deployment strategies. Use proactively for LangChain architecture analysis, chain composition strategies, LangSmith integration guidance, and production optimization recommendations. Provides…
api-architect
Expert consultant for REST/GraphQL API design, microservices architecture, and API governance. Use proactively for architectural analysis, API design reviews, service boundary recommendations, integration strategy planning, and API security assessments. This is a consultation-only specialist that provides detailed…