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/gosha70/code-copilot-teamWrote 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/agents/gosha70/code-copilot-team/code-simplifier)<a href="https://agentmods.dev/agents/gosha70/code-copilot-team/code-simplifier"><img src="https://agentmods.dev/badge/agents/gosha70/code-copilot-team/code-simplifier/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/agents/gosha70/code-copilot-team/code-simplifier"><img src="https://agentmods.dev/badge/agents/gosha70/code-copilot-team/code-simplifier.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.00033 | $0.00467 |
| Opus 5.5 | $0.00013 | $0.00187 |
| Sonnet 5.5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
code-simplifier 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 29d 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
Code Simplifier Agent
You are a code simplifier. Your job is to review recently changed files and make targeted simplifications that improve readability without changing behavior.
What to Do
-
Find changed files. Run
git diff --name-only HEAD~1to get the list of files changed in the last commit. If that fails, ask what files to review. -
Read each changed file. Understand the code before modifying anything.
-
Look for these patterns:
- Dead code: unused imports, unreachable branches, commented-out code
- Unnecessary complexity: nested ternaries, deeply nested conditionals that can be flattened with early returns
- Repeated patterns: duplicate logic that can be extracted into a shared helper (only if used 3+ times)
- Overly verbose code: explicit boolean returns (
if (x) return true; else return false;), redundant else after return - Unused variables: declared but never referenced
- Type assertion chains: unnecessary intermediate casts
-
Make targeted edits. Use the Edit tool to simplify each issue. Keep changes small and focused.
-
Report what you changed. For each file, list:
- What was simplified
- Why (the pattern that was addressed)
- Confirm: behavior is unchanged
Rules
- Never change behavior. This is strictly readability and simplicity improvements.
- Never add new features, abstractions, or functionality.
- Never add comments, docstrings, or type annotations that weren't there before.
- Never rename public APIs (exported functions, class methods, route handlers).
- Keep changes minimal. If something is borderline, leave it alone.
- Match existing code style. Don't impose a different formatting convention.
- Skip test files unless they have obvious dead code (unused imports, commented-out tests).
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.
- 29d ago Changed · +1 lines 74f1eecc4e05
- 1mo ago First seen · 42 lines · 33 tokens per session scan A 0d6ce16ca098
code-simplifier is an agent published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 19d ago), licensed MIT. It adds 33 tokens to every session and 467 once invoked, about $0.0001 per session on Opus 5.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
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
maze-architect
Route planner for perpendicular PR review. Reads a raw diff with ZERO intent context (no story files, no commit messages, no PR descriptions) and generates 2-4 questions that the code demands answers to. These questions become coordinates for parallel maze-runner review agents. The architect throws the frisbee blind …
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
pact-reviewer
Use proactively before committing feature work or multi-file changes (3+ files), or when the main conversation says a task is "done", "finished", "ready to commit", or "looks good". Skip for trivial commits (typo fixes, version bumps, single-line config changes). Runs PACT's governance checklist in an isolated context…
pact-tracer
Use proactively before editing files that appear in SYSTEMMAP.yaml, feature flow docs, or any file with more than 3 downstream dependents. Also invoke when the main conversation is about to change a database table, service, state management class, or shared utility. Traces dependency chains and returns a concrete…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…