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 agentmods add skills/samibs/skillfoundry/guardloopnpx skills add samibs/skillfoundry --skill guardloopgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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 | $0.00012 | $0.01680 |
| Opus 5 | $0.00006 | $0.00840 |
| Sonnet 5 | $0.00002 | $0.00336 |
| Haiku 4.5 | $0.00001 | $0.00168 |
Grade A, and why
guardloop 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/guardloop — Adaptive Learning Guardrail Engine
Analyzes recurring failure patterns harvested from coding sessions and promotes them into enforced rules in
agents/_guardloop-rules.md.Powered by GuardLoop (github.com/samibs/guardloop.dev) × SkillFoundry.
Usage
/guardloop Pattern frequency report (default)
/guardloop analyze Same as above — full report with candidates
/guardloop promote Promote ready patterns → agents/_guardloop-rules.md
/guardloop scan Scan codebase for known failure patterns right now
/guardloop status Show pattern counts + hook health
/guardloop reset Reset all pattern counters (use after major cleanup)
Instructions
You are the GuardLoop Engine — the self-learning layer that converts observed LLM failures into enforced guardrails. You learn from this project's real history, not from theoretical rules.
Default / analyze — Pattern Frequency Report
Step 1: Run analysis script
bash scripts/guardloop-analyze.sh
Step 2: Read the pattern state directly for additional context
.claude/hooks/state/guardloop-patterns.json
Step 3: Read last 5 entries tagged guardloop from the knowledge base to show recent examples
memory_bank/knowledge/errors-universal.jsonl
(filter lines where "tags" array contains "guardloop", take the last 5)
Step 4: Present the report:
GuardLoop Analysis — <date>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Patterns tracked: 10
Total detections: N
Ready to promote: N
Already promoted: N
[table from script output]
Recent detections:
[last 3 from knowledge base]
If there are patterns ready to promote, recommend: Run /guardloop promote to generate guardrails.
promote — Promote Patterns to Agents
Step 1: Run promotion script
bash scripts/guardloop-promote.sh
Step 2: Read the updated agents/_guardloop-rules.md to confirm the new rules
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.
- yesterday First seen · 226 lines · 12 tokens per session scan A 3137de7274d0
guardloop is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,680 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
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…