Borrowing it
Nothing to install: this file belongs to TheSmokeDev/taskchad-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheSmokeDev/taskchad-os/master/.claude/commands/core_piv_loop/prime-tools.mdgit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/thesmokedev/taskchad-os/prime-tools)<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/prime-tools"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/prime-tools.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.1 | $0.00000 | $0.00381 |
| Opus 5 | $0.00000 | $0.00191 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
prime-tools 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 6d 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
Prime for Tool Development
Load tool development patterns from Module 3 to prepare for building agent tools.
Context
You are about to work on building or modifying agent tools that will be used by Pydantic AI agents. Load the comprehensive patterns and best practices we established in Module 3 for writing agent-optimized tool docstrings.
Read
Read the tool docstring patterns: @.agents/reference/adding_tools_guide.md
Process
Understand and internalize:
- Core Philosophy - How agent tool docstrings differ from standard docstrings
- 7 Required Elements - One-line summary, "Use this when", "Do NOT use", Args with guidance, Returns, Performance Notes, Examples
- Agent Perspective - Writing for LLM comprehension and tool selection
- Token Efficiency - Documenting token costs and optimization strategies
- Anti-patterns - Common mistakes that confuse agents
- Template Structure - The exact format to follow
Pay special attention to:
- "Use this when" (affirmative guidance for tool selection)
- "Do NOT use" (negative guidance to prevent tool confusion)
- Performance Notes (token costs, execution time, limits)
- Realistic examples (not "foo", "bar", "test.md")
Report Back
Provide a concise summary with:
Key Principles (5 bullets max)
- [What are the core principles you understood?]
Critical Distinctions
- [What makes agent tool docstrings different from standard docstrings?]
- [Why does "Do NOT use" matter?]
Template Internalized
- [Confirm you understand the structure you'll follow]
Ready to Apply
- [One sentence confirming you're ready to write agent-optimized tool docstrings]
Keep it scannable - I want to verify understanding in 30 seconds.
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.
- 6d ago First seen · 52 lines · 0 tokens per session scan A 5836f37931db
prime-tools is a command published in the GitHub repository TheSmokeDev/taskchad-os (23 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 381 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 commands, from other repositories
tokenless-stats
Show Tokenless compression statistics.
agent-brain-cache
View embedding cache metrics or clear the cache.
migrate_plans
Automatically review all plans in .cursor/plans/, determine relevance, and migrate relevant ones to docs/proposals/ for future consideration.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
scorecard
Run a repeatable weekly health check. Score Brain OS out of 100. Compare week-over-week.
remember
Save text as a project memory in Rembric.