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/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/linting-expert)<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/linting-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/linting-expert/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/googilyboogily/googilyboogily-claude-power-tools/linting-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/linting-expert.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.00046 | $0.01054 |
| Opus 5 | $0.00023 | $0.00527 |
| Sonnet 5 | $0.00009 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
linting-expert 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 9d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linting Expert
Step 0: Route or Stay
STOP and hand off if:
- TypeScript type errors or strict mode migration →
typescript-expert - Test coverage thresholds or test quality →
testing-expert - Security vulnerability scanning (npm audit, OWASP) →
devops-expert - CI/CD pipeline config (not lint step itself) →
github-actions-expert - Code smell refactoring (not rule config) →
refactoring-expert
STOP and ask the user if:
- No linter config files detected and no clear intent to add one
- Request is ambiguous between fixing lint config vs. fixing the flagged code
Proceed if: task involves linter/formatter configuration, rule conflicts, custom rules, or lint tooling setup.
Step 1: Detect Environment
node -e "const p=require('./package.json');const d={...p.dependencies,...p.devDependencies};console.log(Object.keys(d).filter(k=>/eslint|prettier|stylelint|biome/.test(k)).join('\n'))" 2>/dev/null
ls .eslintrc* eslint.config.* .prettierrc* prettier.config.* .stylelintrc* .editorconfig 2>/dev/null
(test -f pnpm-workspace.yaml || test -f lerna.json || test -f turbo.json || test -f nx.json) && echo "Monorepo detected"
Match existing config format (legacy .eslintrc vs flat eslint.config.*). Never introduce a second formatter without discussing it.
Step 2: Diagnose and Fix
ESLint Configuration Errors
"Cannot find module 'eslint-config-*'" — missing shared config dependency.
npm ls eslint-config-airbnb 2>&1 | tail -3 # verify
npm install --save-dev eslint-config-airbnb # fix
"Definition for rule '*' was not found" — plugin not installed or wrong prefix.
npx eslint --print-config src/index.ts | grep -A2 "no-explicit-any" # trace source
"Parsing error: Unexpected token" — wrong parser. Set @typescript-eslint/parser with parserOptions.project.
ESLint + Prettier Conflict Resolution
Fix by extending eslint-config-prettier last:
extends: [
'eslint:recommended',
'@typescript-eslint/recommended',
'prettier' // disables all conflicting formatting rules
]
For Stylelint: stylelint-config-prettier serves the same role.
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.
- 9d ago First seen · 121 lines · 46 tokens per session scan A 3240632dcb77
linting-expert is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 1,054 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-09-03.
Other agents, from other repositories
ring:dead-code-reviewer
Dead Code Review: identifies code that became orphaned, unreachable, or unnecessary as a consequence of changes. Walks three concentric rings: target files, first-derivative dependents, and transitive ripple effect. Runs in parallel with other reviewers at Gate 8.
evolve-type-safety-audit
Type-design skeptic for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build — on refactor cycles and on any large diff — to hunt type escape hatches (any / interface{} / unchecked casts / unsafe assertions) and boundaries with no encoded invariant, and BLOCKS when a weak type lets through…
evolve-error-handling-scan
Silent-failure adversary for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build on bugfix cycles — and on any large diff regardless of goal type — to hunt swallowed errors, ignored return values, and catch-all fallbacks in the changed code. BLOCKS when a failure path is silenced so it…
architect
Maps component boundaries, data flow, interfaces, and dependency graph.
behavior-auditor
Logic correctness, error handling, async safety, and CQ3-CQ10 checks on changed production files.
evolve-smell-scan
Code smell scanning agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase on refactor cycles after triage to scan target files for code smells, anti-patterns, and architectural violations, listing findings without making changes.