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 AbdullahMalik17/malikclaw --skill guardian-self-evolutiongit clone --depth 1 https://github.com/AbdullahMalik17/malikclawWrote 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/abdullahmalik17/malikclaw/guardian-self-evolution)<a href="https://agentmods.dev/skills/abdullahmalik17/malikclaw/guardian-self-evolution"><img src="https://agentmods.dev/badge/skills/abdullahmalik17/malikclaw/guardian-self-evolution.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.00025 | $0.00186 |
| Opus 5 | $0.00013 | $0.00093 |
| Sonnet 5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
guardian-self-evolution 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 7d 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
🛡️ Guardian Self-Evolution Skill
Use this skill when auditing codebase health, fixing runtime errors autonomously, or running performance benchmarks.
Workflow Phases
- Diagnosis: Run
go testandgolangci-lintto gather failure traces. - Patch Generation: Formulate minimal diff patch addressing root cause.
- Sandbox Verification: Apply patch, verify tests pass, ensure no memory regressions (<10MB ceiling).
- Learning Store Update: Commit successful repair pattern to
LearningStorefor future zero-shot resolution.
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.
- 7d ago First seen · 19 lines · 25 tokens per session scan A 0de576df60e6
guardian-self-evolution is a skill published in the GitHub repository AbdullahMalik17/malikclaw (15 stars, last pushed 11d ago), licensed MIT. It adds 25 tokens to every session and 186 once invoked, about $0.0001 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 skills, from other repositories
agent-qa-debug-fix
Debug, patch, and verify failed Agent QA runs from MCP evidence, artifacts, logs, and local code without hiding product or infrastructure defects.
debug-loop
Use when diagnosing failing tests, stack traces, and repeated errors with a hypothesis-driven debug loop.
red-green-testing
Use when writing failing tests first, running red-green cycles, and keeping regression tests focused.
autonomous-testing
!cat skills/shared/protocols/qa-test-protocol.md 2>/dev/null || echo "=== QA Test Protocol not loaded ===".
cige-product-defect-escalation
Invoked by cige-failure-classification when a run is classified as a Product Defect: execution reached the system under test, the environment is healthy, execution steps are current — but the outcome does not match Intent.
cige-stale-execution-repair
Invoked by cige-failure-classification in two situations: Outdated Test Logic (Mode A — repair Execution[]) and a confirmed False Positive (Mode B — strengthen Guardrails). These are different repairs with different targets; do not conflate them.