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/vahlame/create-vkm-kit/vkm-implementergit clone --depth 1 https://github.com/Vahlame/create-vkm-kitWrote 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/agents/vahlame/create-vkm-kit/vkm-implementer)<a href="https://agentmods.dev/agents/vahlame/create-vkm-kit/vkm-implementer"><img src="https://agentmods.dev/badge/agents/vahlame/create-vkm-kit/vkm-implementer.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.00055 | $0.00290 |
| Opus 5 | $0.00028 | $0.00145 |
| Sonnet 5 | $0.00011 | $0.00058 |
| Haiku 4.5 | $0.00006 | $0.00029 |
Grade A, and why
vkm-implementer 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 24 lines · 55 tokens per session scan A 9d0c72d12e69
vkm-implementer is an agent published in the GitHub repository Vahlame/create-vkm-kit (4 stars, last pushed 13d ago), with no licence file. It adds 55 tokens to every session and 290 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-31.
Other agents, from other repositories
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
inkwell-project-onboarder
Use proactively whenever work starts in a project directory and Inkwell (mcpinkwellsearch / list / tags) has no hub entry for it. Investigates the project's purpose, stack, and connections to other projects, then writes the required Inkwell hub + linked entries so future sessions (in this project or another) have the…
orchestrator
Role: Coordinate planner and workers in multi-agent PDF pipeline Workflow: pdf-pipeline Namespace: team:eng.
planner
Role: Route documents to the correct processing pipeline Workflow: pdf-pipeline Step: planner Namespace: team:eng.
ocr_worker
Role: Extract text from scanned PDFs via OCR Workflow: pdf-pipeline Step: ocr Namespace: team:eng.
executor
Builder to an ALREADY-DECIDED spec (the model split: the main session designs; the executor builds). Use for: building a designed slice/chunk, test writing, mechanical refactors with an objective gate (typecheck, test suites, byte-replay). The spec — normally a file at projects/ /plans/YYYY-MM-DD- .md, named in the…