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 caioribeiroclw-pixel/pluribus --skill skill-policy-receiptsgit clone --depth 1 https://github.com/caioribeiroclw-pixel/pluribusWrote 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/caioribeiroclw-pixel/pluribus/skill-policy-receipts)<a href="https://agentmods.dev/skills/caioribeiroclw-pixel/pluribus/skill-policy-receipts"><img src="https://agentmods.dev/badge/skills/caioribeiroclw-pixel/pluribus/skill-policy-receipts/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/caioribeiroclw-pixel/pluribus/skill-policy-receipts"><img src="https://agentmods.dev/badge/skills/caioribeiroclw-pixel/pluribus/skill-policy-receipts.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.00055 | $0.00556 |
| Opus 5 | $0.00028 | $0.00278 |
| Sonnet 5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
skill-policy-receipts 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 11d 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
Skill Policy Receipts
This Skill turns natural-language guardrails into an inspectable policy receipt.
Preflight: decide before writing
Before creating or editing files:
- List intended targets using coarse paths or globs.
- For each target, decide
allowedorrefused. - Give a short reason.
- If any target is refused, stop before writing.
- Emit a receipt with
write_started=falseandstopped_at="policy_refused".
Receipt shape:
{
"receipt_type": "skill.policy.v1",
"skill": "skill-policy-receipts",
"policy_scope": "<short policy name>",
"targets": [
{
"target": "<coarse path or glob>",
"decision": "allowed|refused",
"reason": "<short reason>"
}
],
"write_started": false,
"post_write_guard": "not_run",
"stopped_at": "policy_refused|all_targets_allowed"
}
Do not include raw prompts, code, secrets, customer data, stack traces, or full tool output.
Write only after all targets are allowed
If every target is allowed:
- Emit or state
stopped_at="all_targets_allowed". - Perform the write.
- Run the configured post-write guard.
- Emit whether the guard passed or failed.
Post-write receipt shape:
{
"receipt_type": "skill.policy.v1",
"skill": "skill-policy-receipts",
"policy_scope": "<short policy name>",
"write_started": true,
"post_write_guard": "passed|failed|not_configured",
"stopped_at": "guard_passed|guard_failed"
}
Example policy: no internal-service unit tests
Policy:
Do not generate unit tests for internal services. If the requested test imports
internal/,@/internal, or a known private service module, refuse before writing and explain the safer target.
Example guard:
grep -R "from ['\"]\.\./\.\./internal\|from ['\"]@/internal\|require(['\"]@/internal" \
-- '*test.*' '*spec.*'
If the grep finds a match in generated tests, stop and report post_write_guard="failed".
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.
- 11d ago First seen · 78 lines · 55 tokens per session scan A 633b4da097b5
skill-policy-receipts is a skill published in the GitHub repository caioribeiroclw-pixel/pluribus (13 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 556 once invoked, about $0.0003 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
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.
skill-push
Create and push reusable skills to SkillNote from Codex when repeated instructions are detected or the user says "create a skill", "save this pattern", "push a skill". Guides drafting, review, collection selection, and publishing.
skillnote-doctor
A diagnostic tool for OpenClaw agents -- checks skill registry connectivity, AGENTS.md setup, config file validity, and installed skill health. Use when your setup seems broken, skills aren't loading, or you want to audit your agent's configuration.
collection
Choose which SkillNote skill collection is active for this Codex project. Use when the user says "change collection", "switch skills", "use frontend skills", or "show collections".
complete-skill
Rate a SkillNote skill after using it in Codex. Called after applying a skill to record a 1-5 rating and outcome.
deep-dive
2-stage pipeline: trace (causal investigation) -> deep-interview (requirements crystallization) with 3-point injection.