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 sofiahernandes/margaret --skill margaret-guardgit clone --depth 1 https://github.com/sofiahernandes/margaretWrote 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/sofiahernandes/margaret/margaret-guard)<a href="https://agentmods.dev/skills/sofiahernandes/margaret/margaret-guard"><img src="https://agentmods.dev/badge/skills/sofiahernandes/margaret/margaret-guard.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.00184 | $0.00599 |
| Opus 5 | $0.00092 | $0.00300 |
| Sonnet 5 | $0.00037 | $0.00120 |
| Haiku 4.5 | $0.00018 | $0.00060 |
Grade A, and why
margaret-guard 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
Review changed code for HIGH-CONFIDENCE, exploitable security vulnerabilities only — not style, not theoretical hardening, not pre-existing issues outside the diff.
Categories
Input validation (SQL/command/XXE/template/NoSQL injection, path traversal) · auth (bypass, privilege escalation, session/JWT flaws) · crypto/secrets (hardcoded keys, weak algorithms, bad key storage/randomness, cert bypass) · code execution (insecure deserialization, eval injection, XSS) · data exposure (secrets/PII in logs, endpoint leakage, debug info).
Confidence
Only report what you're >80% sure is actually exploitable. Local-network-only still counts as HIGH. Never report: DOS/resource exhaustion, secrets on disk if otherwise secured, rate limiting, missing best-practice hardening with no concrete exploit path, test-only files, outdated third-party libraries.
Method
Trace data flow from user input to sensitive operations. Compare against this codebase's own established sanitization/auth patterns — a deviation from the project's own norm is a stronger signal than an abstract rule. Read the code, don't try to reproduce it.
Before reviewing, check for two optional repo config files — neither is required, missing means no-op, same behavior as without them:
.margaret/security-instructions.md: extra categories/context to fold into Categories above, never a replacement for it..margaret/security-exclude: one path glob per line (e.g.vendor/**); drop any finding whose file matches.
Output
Per finding: file:line, severity (HIGH/MEDIUM only — LOW is noise), category, one-line description, exploit scenario, fix. If nothing clears the bar: say so and stop.
Boundaries
Security only — route over-engineering findings to /margaret-scan. Lists findings, applies no fixes.
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 · 44 lines · 184 tokens per session scan A 3e285555d734
margaret-guard is a skill published in the GitHub repository sofiahernandes/margaret (2 stars, last pushed 24d ago), licensed MIT. It adds 184 tokens to every session and 599 once invoked, about $0.0009 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-31.
Other skills, from other repositories
skillnote
Self-hosted skill registry for OpenClaw. Stores procedures your team writes (name, description, body), syncs them to disk before each task, and collects which-helped/which-failed signals from the agent so the registry improves over time.
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
test-coverage
Use after writing tests to assess coverage quality across structural, mutation, requirements, and API/integration dimensions; organized knowledge for choosing and interpreting coverage analyses.
do-competitively
Execute tasks through competitive multi-agent generation, meta-judge evaluation specification, multi-judge evaluation, and evidence-based synthesis.
create-rule
Use when found gap or repetative issue, that produced by you or implemenataion agent. Esentially use it each time when you say "You absolutly right, I should have done it differently." -> need create rule for this issue so it not appears again.