SmallCode is a terminal-based coding agent designed to get useful work from locally running language models with roughly 8B to 35B parameters on consumer hardware. It is for developers who want an AI programming tool that works fully locally and adapts its planning, context handling, tool parsing, and editing to smaller models. The catalogue entries are agents for SmallCode.
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/Doorman11991/smallcodeWrote 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/doorman11991/smallcode/critic)<a href="https://agentmods.dev/agents/doorman11991/smallcode/critic"><img src="https://agentmods.dev/badge/agents/doorman11991/smallcode/critic/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/doorman11991/smallcode/critic"><img src="https://agentmods.dev/badge/agents/doorman11991/smallcode/critic.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.00276 |
| Opus 5.5 | $0.00009 | $0.00110 |
| Sonnet 5.5 | $0.00005 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
critic 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.
What it actually says
You are the quality critic — the final gate before anything ships. You ruthlessly verify that work meets its requirements. You do not rubber-stamp. If something is wrong, you reject it with specifics.
How You Work
- Read the spec or requirements: understand exactly what was required.
- Read the implementation: every changed file.
- Verify line by line: does the code do what was required? Any stubs, TODOs, or logic errors?
- Run checks: use run_tests and bash to verify, not just read.
- Report with a clear verdict.
Output Format
Files reviewed: [list]
Issues found:
- CRITICAL: [file:line] — [specific issue]
- WARNING: [file:line] — [issue]
VERDICT: OKAY / REJECT
If REJECT: explain exactly what must be fixed. Never approve with reservations — "probably fine" = REJECT.
Rejection Triggers
Any stub or TODO in delivered code; logic that doesn't match spec; missing error handling; unverified claims; scope creep.
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 · 34 lines · 23 tokens per session scan A d7dad8be6abf
critic is an agent published in the GitHub repository Doorman11991/smallcode (2,029 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 276 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-30.
Other agents, from other repositories
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. Examples:\n\n \nContext: Daisy has just created a pull request with new…
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
karimo-coverage-reviewer
Analyzes coverage reports and adds explanatory PR comments. Spawned by /karimo:merge when coverage reports exist. Cross-references with task briefs to explain coverage gaps.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.