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 commands/001tmf/blatant-why/set-profilegit clone --depth 1 https://github.com/001TMF/blatant-whyWrote 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/001tmf/blatant-why/set-profile)<a href="https://agentmods.dev/commands/001tmf/blatant-why/set-profile"><img src="https://agentmods.dev/badge/commands/001tmf/blatant-why/set-profile.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.00015 | $0.00568 |
| Opus 5 | $0.00008 | $0.00284 |
| Sonnet 5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
by:set-profile 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 5d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/set-profile — Switch Model Profile
Change the model profile used for spawning agents. This controls which Claude model each agent type uses, trading cost for capability.
Instructions
This command does NOT spawn agents. It reads and writes config directly.
Step 1: Validate argument
The argument must be one of: quality, balanced, budget.
If missing or invalid, show usage:
Usage: /by:set-profile <quality|balanced|budget>
Profiles control which models are used for each agent:
quality — Best results, highest cost (Opus for most agents)
balanced — Good results, moderate cost (Sonnet for most agents)
budget — Fast iteration, lowest cost (Haiku where possible)
Step 2: Read current config
CONFIG_FILE=".by/config.json"
if [ ! -f "$CONFIG_FILE" ]; then
mkdir -p .by
echo '{"model_profile": "balanced"}' > "$CONFIG_FILE"
fi
Read the current config file.
Step 3: Update profile
Write the new model_profile value to .by/config.json, preserving
any other fields in the config.
Step 4: Display profile table
Show the complete model assignment table for the selected profile:
Model Profile: {selected}
Agent quality balanced budget
------------------------- ---------- ---------- ----------
by-research opus sonnet sonnet
by-design opus sonnet sonnet
by-screening sonnet sonnet haiku
by-campaign opus opus sonnet
by-knowledge sonnet haiku haiku
by-verifier sonnet sonnet sonnet
by-plan-checker sonnet sonnet haiku
by-environment sonnet sonnet haiku
by-lab opus opus sonnet
by-evaluator opus sonnet sonnet
by-visualization sonnet sonnet haiku
by-diversity sonnet sonnet haiku
by-epitope opus sonnet sonnet
by-humanization opus sonnet haiku
by-liability-engineer sonnet sonnet haiku
by-formatter sonnet haiku haiku
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.
- 5d ago First seen · 80 lines · 15 tokens per session scan A 32a95f91dadc
by:set-profile is a command published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 19d ago), licensed MIT. It adds 15 tokens to every session and 568 once invoked, about $0.0001 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-30.
Other commands, from other repositories
scaffold-fastmcp-v2
Scaffold a new FastMCP server with standard Life Sciences project structure following ADR-001 patterns.
graphiti-health
Display unified real-time health status for Neo4j Aura and Graphiti services.
graphiti-aura-stats
Generate production graph statistics for Neo4j Aura analytics and capacity planning.
graphiti-docker-stats
Generate development environment statistics for Docker Neo4j namespace management.
scaffold-fastmcp
Scaffold a new FastMCP server with standard Life Sciences project structure following ADR-001 patterns.
graphiti-verify
Run Day 1 verification sequence to confirm environment is working.