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/Rune-kit/runeWrote 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/rune-kit/rune/logic-guardian)<a href="https://agentmods.dev/agents/rune-kit/rune/logic-guardian"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/logic-guardian/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/rune-kit/rune/logic-guardian"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/logic-guardian.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.00041 | $0.00294 |
| Opus 5.5 | $0.00016 | $0.00118 |
| Sonnet 5.5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
logic-guardian 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 logic-guardian skill — Rune's business logic protector.
Quick Reference
Workflow:
- Load Manifest — read
.rune/logic-manifest.jsonor generate if first time - Validate Against Codebase — check for drift, verify functions exist, detect new functions
- Pre-Edit Gate — before ANY edit to manifested file: display component spec, require agent to state what WILL be preserved
- Generate Manifest (first-time) — scan logic-heavy files, extract functions/parameters/conditionals, classify, map dependencies
- Post-Edit Validation — re-read file, check for removed functions, changed signatures, run tests
- Update Manifest — persist changes and save ADRs
Critical Rules:
- MUST load manifest before ANY edit to manifested file
- MUST NOT allow edits without explicitly listing what will be preserved
- MUST alert on function removal — accidental deletion is the #1 threat
- MUST run tests after editing manifested files
Read skills/logic-guardian/SKILL.md for the full specification.
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 · 27 lines · 41 tokens per session scan A e96970e0f4d7
logic-guardian is an agent published in the GitHub repository Rune-kit/rune (86 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 294 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-30.
Other agents, from other repositories
insistir-reviewer
Cross-review agent for insistir multi-agent orchestration. Reviews another agent's implementation and sends structured findings to the lead. Read-only — cannot edit or write files. Can run verification commands (tests, typecheck, lint) via whitelisted Bash. Enforces quality without gatekeeping. Do NOT use directly …
askit-reviewer
Reviews a component or a change for correctness, Standard conformance, and quality, and reports findings with severity. Use when delegating a judgment review that goes beyond the deterministic checks - the qualitative counterpart to askit-evaluator.
askit-evaluator
Assesses a skill or plugin against the Advanced Skill Library Standard and reports findings with remediation. Use when delegating conformance assessment - the bounded read-only role behind askit-evaluate.
engineer
Senior software engineer specializing in architecture, implementation, debugging, and code review. Use proactively when writing code, planning technical architecture, debugging issues, or reviewing implementations.
reality-checker
Final quality gate that defaults to "NEEDS WORK". Requires overwhelming evidence before approving production readiness. Stops fantasy approvals and premature sign-offs.
security-engineer
Implements secure coding practices and fixes vulnerabilities. Expert in OWASP, authentication, encryption. Reviews code with a security-first mindset.