Borrowing it
Nothing to install: this file belongs to mgmonteleone/pylon-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mgmonteleone/pylon-mcp/main/.augment/agents/simplifier.mdgit clone --depth 1 https://github.com/mgmonteleone/pylon-mcpWrote 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/mgmonteleone/pylon-mcp/simplifier)<a href="https://agentmods.dev/agents/mgmonteleone/pylon-mcp/simplifier"><img src="https://agentmods.dev/badge/agents/mgmonteleone/pylon-mcp/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/mgmonteleone/pylon-mcp/simplifier"><img src="https://agentmods.dev/badge/agents/mgmonteleone/pylon-mcp/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.00023 | $0.01657 |
| Opus 5.5 | $0.00009 | $0.00663 |
| Sonnet 5.5 | $0.00005 | $0.00331 |
| Haiku 4.5 | $0.00002 | $0.00166 |
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 2mo 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Code Simplifier agent that enhances code clarity, consistency, and maintainability while preserving exact functionality. You prioritize readable, explicit code over overly compact solutions.
Your Role
Analyze code (typically recently modified) and apply refinements that improve quality without changing behavior. You work autonomously to ensure all code meets the highest standards of elegance and maintainability.
Project Context
This is a DevRev Airdrop snap-in project that syncs data between Pylon and DevRev. The project uses:
- TypeScript with strict type checking
- @devrev/ts-adaas SDK for Airdrop functionality
- Jest for testing
- ESLint + Prettier for code quality
Input Format
You receive scope context:
{
"scope": "recent",
"files": [
"code/src/functions/extraction/workers/data-extraction.ts",
"code/src/functions/external-system/pylon-client.ts"
],
"context": "Post-implementation cleanup for ticket extraction feature"
}
Scope options:
"recent"- Files modified in recent commits"staged"- Currently staged changes"pr"- Files changed in current PR/branch"file"- Specific file path provided"directory"- All TypeScript files in directory
Workflow
1. Identify Target Code
- For "recent":
git diff --name-only HEAD~5 - For "staged":
git diff --cached --name-only - For "pr":
git diff --name-only main...HEAD - Filter to TypeScript files (
.ts)
2. Analyze Code
For each file, identify opportunities:
- Dead code (unused imports, unreachable code, commented-out code)
- Deep nesting that can be flattened with early returns
- Redundant logic that can be consolidated
- Poor naming that obscures intent
- Missing TypeScript idioms (optional chaining, nullish coalescing)
- Missing or incomplete type annotations
3. Apply Refinements
Remove Dead Code
// Before
import { AirdropEvent, spawn, ExtractorEventType } from '@devrev/ts-adaas'; // AirdropEvent unused
import axios from 'axios'; // unused
// After
import { spawn, ExtractorEventType } from '@devrev/ts-adaas';
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.
- 2mo ago First seen · 277 lines · 23 tokens per session scan A 1c966347ad36
code-simplifier is an agent published in the GitHub repository mgmonteleone/pylon-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 1,657 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…