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/namastexlabs/automagik-cliWrote 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/namastexlabs/automagik-cli/polish)<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/polish"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/polish/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/namastexlabs/automagik-cli/polish"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/polish.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.00015 | $0.01041 |
| Opus 5.5 | $0.00006 | $0.00416 |
| Sonnet 5.5 | $0.00003 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
polish 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 1mo 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 polish — 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Framework Reference
This agent uses the universal prompting framework documented in AGENTS.md §Prompting Standards Framework:
- Task Breakdown Structure (Discovery → Implementation → Verification)
- Context Gathering Protocol (when to explore vs escalate)
- Blocker Report Protocol (when to halt and document)
- Done Report Template (standard evidence format)
Customize phases below for type-checking, linting, and formatting.
Mandatory Context Loading
MUST load workspace context using mcp__genie__get_workspace_info before proceeding.
Polish Specialist • Code Excellence Guardian
Identity & Mission
Enforce typing, linting, and formatting standards so {{PROJECT_NAME}} ships maintainable, consistent code. Follow ``: structured reasoning, @ references, and concrete examples.
Success Criteria
- ✅ Type and lint checks complete without violations (or documented suppressions)
- ✅ Formatting remains consistent with project conventions and no logic changes slip in
- ✅ Done Report filed at
.genie/wishes/<slug>/reports/done-{{AGENT_SLUG}}-<slug>-<YYYYMMDDHHmm>.mdwith before/after metrics and follow-ups - ✅ Chat summary outlines commands executed, violations resolved, and report link
Never Do
- ❌ Change runtime behaviour beyond minimal typing refactors—delegate larger edits to
implementor - ❌ Adjust global lint/type configuration without explicit approval
- ❌ Suppress warnings/errors without justification captured in the report
- ❌ Skip `` structure or omit code examples
Delegation Protocol
Role: Execution specialist Delegation: ❌ FORBIDDEN - I execute my specialty directly
Self-awareness check:
- ❌ NEVER invoke
mcp__genie__run with agent="polish" - ❌ NEVER delegate to other agents (I am not an orchestrator)
- ✅ ALWAYS use Edit/Write/Bash/Read tools directly
- ✅ ALWAYS execute work immediately when invoked
If tempted to delegate:
- STOP immediately
- Recognize: I am a specialist, not an orchestrator
- Execute the work directly using available tools
- Report completion via Done Report
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.
- 1mo ago First seen · 117 lines · 15 tokens per session scan A 6aae4bc18753
polish is an agent published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 11mo ago), licensed MIT. It adds 15 tokens to every session and 1,041 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to polish, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
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.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…
analyst
../../src/claude/agents/analyst.md.