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/llcoolblaze/claude-boris/modegit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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/llcoolblaze/claude-boris/mode)<a href="https://agentmods.dev/commands/llcoolblaze/claude-boris/mode"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/mode.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.00025 | $0.00912 |
| Opus 5 | $0.00013 | $0.00456 |
| Sonnet 5 | $0.00005 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
mode scanned grade A with 1 finding 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
!`cat .claude/current-mode 2>/dev/null || echo "code"` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mode Control
Current Mode
!cat .claude/current-mode 2>/dev/null || echo "code"
Mode Switch
Target Mode: $ARGUMENTS
Available Modes
🏗️ Architect Mode
Purpose: Design and planning only Access: Read-only, no file modifications Use for: System design, architecture review, planning
💻 Code Mode (Default)
Purpose: Active development Access: Full tool access Use for: Implementation, bug fixes, features
🔍 Debug Mode
Purpose: Investigation and diagnosis Access: Read-heavy, limited writes Use for: Troubleshooting, root cause analysis
👀 Review Mode
Purpose: Code review only Access: Strictly read-only Use for: PR review, code audit
🔒 Audit Mode
Purpose: Security and compliance Access: Read-only with full logging Use for: Security scans, compliance checks
Mode Switching Protocol
1. Validate Target Mode
Valid modes: architect, code, debug, review, audit
2. Save Current Context
Before switching:
- Note current work state
- Save any pending changes
- Update Memory Bank
3. Apply Mode
echo "$TARGET_MODE" > .claude/current-mode
echo "$(date +%Y-%m-%d_%H:%M:%S) MODE_SWITCH to $TARGET_MODE" >> .claude/audit/mode.log
4. Announce Mode Change
🎛️ Mode Changed
From: [previous mode]
To: [new mode]
Capabilities:
✅ [What you CAN do]
❌ [What you CANNOT do]
To change: /mode [mode-name]
5. Mode-Specific Behaviors
Architect Mode:
I am now in Architect mode.
I WILL:
- Read and analyze code
- Create design documents
- Suggest architectural improvements
- Delegate to other agents
I WILL NOT:
- Edit source files
- Make commits
- Run modifying commands
Code Mode:
I am now in Code mode.
Full development capabilities enabled.
All tools available.
Debug Mode:
I am now in Debug mode.
I WILL:
- Investigate issues systematically
- Read logs and error messages
- Add diagnostic output (with confirmation)
I WILL LIMIT:
- Direct code changes
- Refactoring
- Feature additions
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 · 181 lines · 25 tokens per session scan A 24a0e232f81b
mode is a command published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 912 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.