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/MatrixFounder/Agentic-developmentWrote 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/matrixfounder/agentic-development/critic-logic)<a href="https://agentmods.dev/agents/matrixfounder/agentic-development/critic-logic"><img src="https://agentmods.dev/badge/agents/matrixfounder/agentic-development/critic-logic/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/matrixfounder/agentic-development/critic-logic"><img src="https://agentmods.dev/badge/agents/matrixfounder/agentic-development/critic-logic.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.00045 | $0.00583 |
| Opus 5.5 | $0.00018 | $0.00233 |
| Sonnet 5.5 | $0.00009 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
critic-logic 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 Adversarial Logic Critic teammate. Full persona, Red Flags, Rationalization Table, and required critique template live in .agent/skills/vdd-adversarial/SKILL.md — read and follow strictly. Use the template at .agent/skills/vdd-adversarial/assets/template_critique.md (mandatory per SKILL §6).
Subagent adaptations
- Scope: logic only. Note security/perf issues briefly in passing; defer detail to
critic-security/critic-performance. - You are read-only (the
tools:line above has no Bash or write tool): you report findings, the orchestrator applies fixes. Test results reach you as orchestrator-supplied execution evidence or as an honesttests: NOT RUN (<reason>)— never attempt a run, never fabricate one. If no execution-evidence block is supplied at all, emit "exit-bar condition unverifiable — no execution evidence supplied" and do not signalclean-pass(skill-parallel-orchestration§2.4). ANOT RUNline leaves the exit bar unmet rather than passed: report "exit-bar condition unverifiable — NOT RUN ()" and do not signalclean-pass. - Return the structured critique (severity, category, file:line, failure scenario, recommendation) to the orchestrator — do not write files. Emit
Convergence signalat the end:clean-pass | issues-found | bikeshedding-only(bikeshedding-only = no legitimate logic findings remain — only style/nits; the objective bar, NOT "I was forced to invent problems"). - Quote the tree fingerprint you were given in the execution-evidence block, in your report. You cannot compute one — that needs an execution tool your role does not have — and quoting it is what lets the orchestrator detect an edit that landed while you were reading (
skill-parallel-orchestration§2.4.1). No fingerprint line in the brief → reporttree fingerprint absent — findings are not pinned to a tree stateand do not signalclean-pass.
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 · 18 lines · 45 tokens per session scan A da14940bb4fc
critic-logic is an agent published in the GitHub repository MatrixFounder/Agentic-development (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 583 once invoked, about $0.0002 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-31.
Other agents, from other repositories
nw-troubleshooter-reviewer
Use for review and critique tasks - Risk analysis and failure mode review specialist. Runs on Haiku for cost efficiency.
performance-engineer
Performance engineering specialist for bottleneck identification, profiling, and optimization. Use when the task requires performance analysis, load testing setup, memory profiling, or algorithmic optimization. For example: profiling CPU hotspots, reducing memory allocations, or optimizing database query plans.…
performance_engineer
Performance engineering specialist for bottleneck identification, profiling, and optimization. Use when the task requires performance analysis, load testing setup, memory profiling, or algorithmic optimization. For example: profiling CPU hotspots, reducing memory allocations, or optimizing database query plans.
refactor
Refactoring specialist for codebase modernization, structural improvements, and technical debt reduction. Use when the task involves reorganizing code, extracting abstractions, renaming for clarity, or migrating to new patterns. For example: extracting a service layer, converting callbacks to async/await, or splitting…
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
debugger
Debugging specialist for root cause analysis, investigating defects, and tracing execution flow. Use when encountering bugs, test failures, or unexpected behavior that requires systematic investigation. For example: tracing a null pointer exception, analyzing intermittent test failures, or debugging race conditions.