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/davidmatousek/tachi/_readmegit clone --depth 1 https://github.com/davidmatousek/tachiWhat 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.02222 |
| Opus 5 | $0.00000 | $0.01111 |
| Sonnet 5 | $0.00000 | $0.00444 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
_README 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- _README — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Directory
Quick reference for all agents in {{PROJECT_NAME}}.
Agent Roster
| Agent | Role | Lines | Primary Use Cases |
|---|---|---|---|
| architect | System Architect | 269 | Technical design, architecture decisions, technology selection |
| code-reviewer | Code Quality Analyst | 269 | Pull request reviews, code quality assessment, best practices |
| debugger | Root Cause Analyst | 239 | Bug investigation, 5 Whys analysis, error diagnosis |
| devops | Infrastructure Engineer | 291 | Deployment, CI/CD, environment management |
| frontend-developer | Frontend Engineer | 243 | UI implementation, component development, client-side code |
| orchestrator | Workflow Executor | 255 | Multi-agent coordination, parallel wave execution, progress monitoring |
| product-manager | Product Owner | 259 | PRD creation, requirements, scope decisions, product vision |
| security-analyst | Security Specialist | 277 | Security reviews, vulnerability assessment, compliance |
| senior-backend-engineer | Backend Engineer | 278 | API development, server-side logic, database operations |
| team-lead | Engineering Lead | 210 | Governance, sign-offs, feasibility, capacity, agent assignments |
| tester | QA Engineer | 187 | Test strategy, test cases, BDD scenarios, quality validation |
| ux-ui-designer | UX/UI Designer | 245 | UI/UX design, user experience, interface design, wireframes |
| web-researcher | Research Specialist | 265 | Web research, documentation lookup, technology investigation |
Total Agents: 13 | Total Lines: 3,287 | Average: 253 lines/agent
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 · 266 lines · 0 tokens per session scan A c29bbb80ac0a
_README is an agent published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,222 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-30.
Other agents, from other repositories
CLAUDE
This guide provides instructions for creating cs- prefixed agents that orchestrate the USAP skill packages.
malware-analyst
Delegates to this agent when the user asks about malware analysis, reverse engineering, binary analysis, disassembly, debugging, sandbox analysis, static analysis, dynamic analysis, or suspicious file triage.
data-exfiltrator
Delegates to this agent when the user wants to test exfiltration and DLP/egress controls during an authorized engagement — DNS tunneling, HTTPS/cloud-storage exfil, ICMP, protocol abuse, and staging — using synthetic/canary data to validate detection. Every technique ships with the egress detection it exercises.
exploit-guide
Delegates to this agent when the user asks about exploitation techniques, attack methodologies, tool configurations for authorized testing, post-exploitation activities, or specific vulnerability exploitation paths.
risk-scorer
Delegates to this agent when the user wants to score and prioritize findings — build CVSS 3.1/4.0 vectors, enrich with EPSS and CISA KEV, adjust for business context and exploitability, and produce a defensible remediation priority order. Distinct from attack-planner (attack-path sequencing) and report-generator…
credential-tester
Delegates to this agent when the user asks about password attacks, credential testing, hash cracking, brute force methodology, default credential checks, password spraying, or needs help with tools like hydra, john, hashcat, medusa, or CrackMapExec for authorized penetration testing engagements.