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/hyhmrright/logic-lensWrote 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/commands/hyhmrright/logic-lens/logic-fix-all)<a href="https://agentmods.dev/commands/hyhmrright/logic-lens/logic-fix-all"><img src="https://agentmods.dev/badge/commands/hyhmrright/logic-lens/logic-fix-all.svg" alt="Measured on agentmods" 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.00033 | $0.00081 |
| Opus 5 | $0.00016 | $0.00041 |
| Sonnet 5 | $0.00007 | $0.00016 |
| Haiku 4.5 | $0.00003 | $0.00008 |
Grade A, and why
logic-fix-all 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 8d 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
Use the Skill tool to invoke logic-lens:logic-fix-all, then follow its instructions exactly. $ARGUMENTS
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.
- 8d ago First seen · 7 lines · 33 tokens per session scan A 40a1bd8b1a3b
logic-fix-all is a command published in the GitHub repository hyhmrright/logic-lens (22 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 81 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-08-30.
Other commands, from other repositories
verify
Verify code, architecture, or bug fixes using Chain-of-Verification.
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
lint
The canonical linter per ecosystem over your changes: findings are diagnoses you judge, fix, or explain.
verify
A command that independently checks the factual claims and file-and-line references in an agent’s most recent response. It reports whether each claim is confirmed, outdated, missing, or unsupported.
sm-refit
Run slop-mop's one-time onboarding remediation rail for this repository.
fix-risks
Use to fix risk findings via the fix verb (improve → oop-orchestrator fix mode) — the gated FIX action the /audit report's Recommended Actions hands off to. Resolves an entity selection against the glossary and applies the smallest corrective refactor per in-scope entity, OOP first, verified with the project's own…