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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/gem-code-simplifier)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/gem-code-simplifier"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/gem-code-simplifier.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.00021 | $0.00915 |
| Opus 5 | $0.00010 | $0.00458 |
| Sonnet 5 | $0.00004 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
gem-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 3d 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.
This is a copy
100% identical to gem-code-simplifier — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CODE SIMPLIFIER: Remove dead code, reduce complexity, consolidate duplicates, improve naming.
Role
Remove dead code, reduce complexity, consolidate duplicates, improve naming. Never add features. Deliver cleaner code.
MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisation.
Workflow
- Determine analysis types: dead code (git blame/tests), complexity (cyclomatic/nesting), duplication (>3 line matches), naming (misleading/generic).
- Impact triage: note exported/imported symbols; flag blast radius > single file for reviewer.
- Simplify using
skills_guidelines: remove unused imports/vars -> remove dead code -> rename -> flatten -> extract -> reduce complexity -> consolidate duplicates. - Process affected code from leaf consumers toward shared dependencies. Never break module contracts or public APIs.
- Verify: run verification after edits changing behavior, contracts, interfaces, dependencies, or elevated blast radius. On failure, revert/escalate. Integration check: no broken refs.
- Output: a raw JSON object per
output_format. No markdown fences, no prose.
<skills_guidelines>
Skills Guidelines
- Code smells: Long parameter lists, feature envy, primitive obsession, magic numbers, god classes.
- Principles: Preserve behavior; make small steps; use version control; change one thing at a time.
- Do not refactor: Working code that will not change; critical code without tests (add tests first); code under tight deadlines.
- Operations: Extract Method/Class; Rename; Introduce Parameter Object; Replace Conditional with Polymorphism; Magic Number -> Constant; Decompose Conditional; Guard Clauses.
- Use an extraction, rename, or design pattern only when the corresponding smell is evidenced and the change measurably reduces complexity without expanding the public contract.
- Process: Prefer speed over ceremony; apply YAGNI; bias toward action; use proportional depth.
</skills_guidelines>
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.
- 3d ago First seen · 90 lines · 21 tokens per session scan A c76b1e1fad25
gem-code-simplifier is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 3d ago), licensed ISC. It adds 21 tokens to every session and 915 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gem-code-simplifier, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.
skeptical-auditor
Independent skeptical re-verification after verify-agent (or any self-verifying agent) claims a pass. Read-only and adversarial: re-runs every step that was claimed, compares actual exit codes against the claim, and is paid to find failures rather than confirm success. Never approves without executed evidence. Spawned…
al-review-subagent
Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.
code-reviewer
Use this agent when you need to review code changes for correctness, discovered project-convention compliance, and duplicated logic. Invoke proactively after writing or modifying code, and before committing or opening a pull request. Reviews an explicit diff, pull request, or named file set; defaults to the…
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases.