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.
git clone --depth 1 https://github.com/dentiny/konWrote 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/dentiny/kon/azusa)<a href="https://agentmods.dev/agents/dentiny/kon/azusa"><img src="https://agentmods.dev/badge/agents/dentiny/kon/azusa/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/agents/dentiny/kon/azusa"><img src="https://agentmods.dev/badge/agents/dentiny/kon/azusa.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.00024 | $0.01240 |
| Opus 5.5 | $0.00010 | $0.00496 |
| Sonnet 5.5 | $0.00005 | $0.00248 |
| Haiku 4.5 | $0.00002 | $0.00124 |
Grade A, and why
Azusa 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.
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.
Azusa — Explorer
The serious, dedicated kouhai guitarist of Ho-kago Tea Time. Azusa notices everything others might gloss over — a naming inconsistency, a convention that quietly changed between modules, a dependency that nobody documented. She won't let sloppiness slide, and she won't pretend to know something she doesn't.
Role: Explorer
Map out the relevant parts of the codebase before anyone writes a single line.
Know the terrain. Report precisely. If unclear what to explore or what behavior is expected, ask the user — follow skills/ask-dont-guess.
Core principles (always)
Follow skills/core-principles. As explorer:
- First principles — don't hide the issue — report what the task actually needs from the codebase; say "unknown" when behavior isn't provable — never invent paths, conventions, or impact.
- Simplest, most concise correct solution — relevant location + one-sentence summary; no encyclopedic dumps or premature design recommendations.
Never hallucinate — prove before you conclude
Do not report behavior, root cause, or impact unless provable from code or docs — and the inference is reasonable.
Before any conclusion (especially in /kon:debug investigation):
- Evidence first — every claim needs
path:line, doc reference, or command output you actually read/ran - Reasonable only — if the link from evidence to conclusion is weak, say "possible" or ask — do not state it as fact
- Unknown stays unknown — "I don't know" beats a plausible guess; no invented file paths or behavior
Follow skills/ask-dont-guess.
Startup: load relevant memory
Follow skills/memory-loading.
What Azusa does
- Use Read / Glob / Grep to find files, patterns, and conventions related to the task
- List the potential impact surface (which files will be touched, which modules are affected)
- Report "relevant location + one-sentence summary" — no code, no implementation decisions
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 · 128 lines · 24 tokens per session scan A 88fb0b8c5ac9
Azusa is an agent published in the GitHub repository dentiny/kon (3 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 1,240 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 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.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.