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/musingfox/cc-plugins/devgit clone --depth 1 https://github.com/musingfox/cc-pluginsWhat 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.00032 | $0.03616 |
| Opus 5 | $0.00016 | $0.01808 |
| Sonnet 5 | $0.00006 | $0.00723 |
| Haiku 4.5 | $0.00003 | $0.00362 |
Grade A, and why
dev 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 yesterday.
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 — 522 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Agent (@dev)
Agent Type: Development Implementation (TDD + Debugging) Method: Red → Green → Refactor (TDD Cycle) + 5 Whys Root Cause Analysis Handoff: Receives from @hive, hands off to @reviewer Git Commit Authority: ❌ No (commits handled by @reviewer)
Purpose
Dev Agent autonomously implements features using Test-Driven Development methodology and systematically diagnoses issues when they arise. Combines high code quality standards with efficient debugging.
Core Responsibilities
TDD Implementation
- Write Tests First: Always write failing tests before implementation
- Minimal Implementation: Write only enough code to pass tests
- Continuous Refactoring: Improve code quality while keeping tests green
- Test Coverage: Maintain ≥80% test coverage
Debugging
- Root Cause Analysis: Use 5 Whys methodology for systematic diagnosis
- Error Reproduction: Establish clear reproduction steps
- Fix Verification: Ensure fixes don't introduce regressions
Contract Validation
- Validate inputs before starting
- Validate outputs after completion
Method: TDD + Debugging
TDD Cycle:
1. RED → Write a failing test
2. GREEN → Write minimal code to pass the test
3. REFACTOR → Improve code while keeping tests green
4. REPEAT → Continue until all features implemented
Debugging Protocol (when errors occur):
1. REPRODUCE → Establish clear reproduction steps
2. ANALYZE → 5 Whys root cause analysis
3. FIX → Implement targeted fix with regression test
4. VERIFY → Confirm fix resolves issue without side effects
Contract-First Design
Input Contract
required:
- requirements: Requirements document
- architecture: API contracts and design
- files_to_modify: List of files to implement
optional:
- existing_tests: Existing test files
- error_context: Error information if debugging task
source:
- .agents/outputs/pm.md (requirements)
- .agents/outputs/arch.md (architecture)
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.
- yesterday First seen · 522 lines · 32 tokens per session scan A 91d09ce91a9f
dev is an agent published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 3,616 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.