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.
npx skills add kiruxich/legitAgent --skill explain-rulegit clone --depth 1 https://github.com/kiruxich/legitAgentWrote 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/skills/kiruxich/legitagent/explain-rule)<a href="https://agentmods.dev/skills/kiruxich/legitagent/explain-rule"><img src="https://agentmods.dev/badge/skills/kiruxich/legitagent/explain-rule/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/skills/kiruxich/legitagent/explain-rule"><img src="https://agentmods.dev/badge/skills/kiruxich/legitagent/explain-rule.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.00040 | $0.00114 |
| Opus 5.5 | $0.00016 | $0.00046 |
| Sonnet 5.5 | $0.00008 | $0.00023 |
| Haiku 4.5 | $0.00004 | $0.00011 |
Grade A, and why
explain-rule 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
Explain rule
Вызови MCP-инструмент explain_rule сервера legitagent.
ruleId — из текста после команды. Если id нет, спроси. en → lang: "en".
Покажи title, message, fix, выдержку, дисклеймер.
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 · 15 lines · 40 tokens per session scan A 9862c93256f9
explain-rule is a skill published in the GitHub repository kiruxich/legitAgent (2 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 114 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 skills, from other repositories
compliance
Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…
pipefy-toolkit-setup
Guide a first-time user through Pipefy AI toolkit setup (Cursor Marketplace plugin, hosted MCP, local install.sh, or Claude Code plugin). Use when the user asks to install Pipefy MCP, connect Claude/Cursor to Pipefy, run /pipefy:install, or set up mcp.pipefy.com. Do not use for day-to-day Pipefy workflows after MCP is…
complyedge-eu-ai-act-check-and-cite
Check this prompt or output against EU AI Act Article 5 and Article 50 rules and cite the article, via the ComplyEdge TrustLint MCP. Use when the user wants agent I/O checked and cited, not system classification, FRIA forms, or C2PA watermarking.
eu-ai-act
Reference knowledge on the EU AI Act (Regulation (EU) 2024/1689): risk tiers, obligations, compliance deadlines including the 2026 AI Omnibus changes, penalties, and scope. Activate when the user asks about the EU AI Act, AI regulation in Europe, high-risk AI compliance, AI transparency or watermarking obligations…