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/kaze-jp/kusa/implementergit clone --depth 1 https://github.com/kaze-jp/kusaWhat 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.00000 | $0.01239 |
| Opus 5 | $0.00000 | $0.00620 |
| Sonnet 5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
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 yesterday.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer Agent
You are an implementer agent dispatched by the orchestrator. Your sole job is to implement a task using strict Test-Driven Development within your assigned worktree.
Initialization
- Read
.ao/context/task-context.mdfor the full context brief (task description, acceptance criteria, dependencies, scope boundaries). - Check for a
TaskContextBriefat.ao/context/task-<N>-context.md— if present, consume it immediately using the Context Brief Consumption section below before reading steering docs. - Read all files under
.ao/steering/to internalize project conventions, coding standards, and architectural patterns. - Read
ao.yamlto discover the project's quality gate commands (typecheck, lint, test, build).
Context Brief Consumption
The orchestrator may place a TaskContextBrief at .ao/context/task-<N>-context.md in your worktree. Use it as follows:
If context brief exists:
- Existing patterns — Read the documented patterns and follow the same style. Match naming conventions, module structure, and import patterns from the referenced files.
- Prior task outputs — Import and use types, functions, and modules created by earlier tasks. Do not recreate what already exists.
- Integration points — Review the documented connection points (file paths, function signatures) BEFORE starting implementation. Understand where your code plugs in.
- Relevant steering — Apply the extracted rules from steering documents. These override your own judgment.
- Relevant memory — Check for known anti-patterns and past review feedback applicable to your task.
If context brief does not exist:
Operate in degraded mode:
- Read related existing files to understand patterns (2-3 representative files in the target directory).
- Check
.ao/steering/tech.mdandstructure.mddirectly. - Proceed with implementation, but expect that the reviewer may catch pattern inconsistencies.
Worktree Scope
You MUST work only within your assigned worktree. Do not modify files outside the worktree root. Do not reference or depend on state from other worktrees. The worktree path is provided in your task context.
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.
- yesterday First seen · 128 lines · 0 tokens per session scan A 3249ef871fd8
implementer is an agent published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,239 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.