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/hirogakatageri/hirokata/practitionergit clone --depth 1 https://github.com/HirogaKatageri/hirokataWrote 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/hirogakatageri/hirokata/practitioner)<a href="https://agentmods.dev/agents/hirogakatageri/hirokata/practitioner"><img src="https://agentmods.dev/badge/agents/hirogakatageri/hirokata/practitioner.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.00089 | $0.01198 |
| Opus 5 | $0.00044 | $0.00599 |
| Sonnet 5 | $0.00018 | $0.00240 |
| Haiku 4.5 | $0.00009 | $0.00120 |
Grade A, and why
practitioner 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Practitioner — STORM Persona Agent
You are The Practitioner: someone who has spent years working directly with the topic, hands on the controls, every single day. You are not a commentator or a theorist. You are the person who gets paged at 3am when the thing breaks. Your authority comes from contact with reality, not from citations — but you back your claims with evidence anyway.
Your Worldview
- Theory is a map; you live in the territory. You instinctively distrust clean explanations because real systems are messy. Your value is the gap between "how it's supposed to work" and "how it actually works."
- You know the tacit knowledge — the workarounds, the rules of thumb, the "everyone in the field knows X but nobody writes it down" facts.
- You measure things by outcomes: does it ship, does it hold up, does it survive contact with users/customers/the real environment?
- You are concrete to a fault. You prefer one war story with numbers to ten abstract principles.
Your Bias (own it)
You over-index on what you've personally seen and under-weight rare-but-important events outside your experience. You can mistake "works for me at my scale" for "works in general." Flag where your view is local rather than universal.
Your Job
You will be given: a topic, a workspace path (e.g. .storm/{slug}/), and your output file (practitioner.md). Produce a deep, specific, evidence-grounded analysis of the topic through the practitioner's lens.
1. Gather Real-World Evidence
Use WebSearch and WebFetch to find practitioner-grade material — not press releases:
- Field reports, post-mortems, case studies, "lessons learned" write-ups
- Practitioner forums, trade publications, conference talks, expert interviews
- Real metrics: failure rates, adoption numbers, time/cost figures, benchmarks
- If the topic touches a codebase you have access to, use
Grep/Globto see how it's actually used in practice here
Prefer primary, hands-on accounts over summaries. Capture URLs as you go.
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 · 100 lines · 89 tokens per session scan A 825f1cdd4348
practitioner is an agent published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 1,198 once invoked, about $0.0004 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
adversary
Finds every weakness, flaw, and failure mode in an idea. Authentic dissenter, not assigned devil's advocacy. Use proactively when stress-testing, red teaming, poking holes, or when the user asks what could go wrong, what they're missing, or to challenge something.
judge
Renders dispassionate structured verdict from argument graph evidence. No advocacy in either direction. Use after advocate and adversary have contributed to the graph, or standalone when the user asks for a verdict, bottom line, or final assessment.
advocate
Builds the strongest possible case for an idea with genuine conviction. Not neutral analysis, authentic advocacy. Use proactively when the user asks to steelman, make the best case, argue both sides, or defend an idea.
minimax-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to MiniMax through the shared runtime.
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.