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/Khar-AG/t-800-agentWrote 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/commands/khar-ag/t-800-agent/t-800-factory)<a href="https://agentmods.dev/commands/khar-ag/t-800-agent/t-800-factory"><img src="https://agentmods.dev/badge/commands/khar-ag/t-800-agent/t-800-factory/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/commands/khar-ag/t-800-agent/t-800-factory"><img src="https://agentmods.dev/badge/commands/khar-ag/t-800-agent/t-800-factory.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.00000 | $0.00171 |
| Opus 5 | $0.00000 | $0.00086 |
| Sonnet 5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
t-800-factory 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 11d 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.
What it actually says
T-800 Factory — создать или внедрить субагента
Обязательно вызови субагента через Task(t-800-factory).
Передай контекст:
- идея нового агента (роль, задачи);
- категория в будущем плагине;
- readonly или с правками файлов;
- кто будет вызывать этого агента;
- что уже есть в
registry/agents-registry.json.
НЕ создавай агента вручную в main chat — делегируй пайплайн Factory.
Если Task(t-800-factory) недоступен:
Task(generalPurpose)
Промпт: полное содержимое agents/t-800-factory.md + registry/agents-registry.json + knowledge-base/13-agent-factory/INDEX.md.
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.
- 11d ago First seen · 21 lines · 0 tokens per session scan A d651b7017590
t-800-factory is a command published in the GitHub repository Khar-AG/t-800-agent (8 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 171 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 commands, from other repositories
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.
pn-audit-performance
Identify and fix backend performance issues — N+1 queries, missing cache layers, blocking I/O, slow queries, and connection pool exhaustion. Surgical backend performance pass.
pn-delight
Add purposeful moments of joy, motion, and personality. Use when the design is correct and complete but feels flat and lifeless.
pn-frontend-redo
Audit-driven frontend remediation on an existing app — baseline audit, slice plan, sequential UI slices with maker-checker gates, preflight, deliver. Use instead of pn-program for same-repo sequential surfaces (Home → fight → chrome). Not for greenfield (pn-design) or parallel vertical slices (pn-program).
pn-audit-api
Surgical API design review — REST conventions, status codes, response shapes, validation, and schema leaks. Use standalone or as part of pn-backend-audit. Outputs a scored fix roadmap.
pn-audit-errors
Standardize error handling — consistent shapes, structured logging, correlation IDs, safe client responses. Surgical command for error handling. Use standalone or as part of pn-backend-audit.