context-receipts

context-receipts is a skill for Claude Code, Codex from caioribeiroclw-pixel/pluribus. It costs 33 tokens per session (2,626 once invoked), scanned A, original, MIT.

A privacy-safe record of what information crosses boundaries during an agent workflow.

In plain words
What is it for?
It helps audit what context was included or left out, track usage attribution, and record remaining uncertainty when context is transferred or reduced.
Why use it?
It makes context selection, summarising, pruning, delegation, and handoffs reviewable without exposing prompts, tool data, secrets, or private content.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions AGENTS.md.

Good fit It helps audit what context was included or left out, track usage attribution, and record remaining uncertainty when context is transferred or reduced.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/caioribeiroclw-pixel/pluribus/context-receipts
Install

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.

Any agent
npx skills add caioribeiroclw-pixel/pluribus --skill context-receipts
Clone the repo
git clone --depth 1 https://github.com/caioribeiroclw-pixel/pluribus

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for context-receipts

README.md
[![agentmods](https://agentmods.dev/badge/skills/caioribeiroclw-pixel/pluribus/context-receipts/github.svg)](https://agentmods.dev/skills/caioribeiroclw-pixel/pluribus/context-receipts)
Your own site
<a href="https://agentmods.dev/skills/caioribeiroclw-pixel/pluribus/context-receipts"><img src="https://agentmods.dev/badge/skills/caioribeiroclw-pixel/pluribus/context-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.

agentmods 80×15 button for context-receipts

Your own site · 80×15
<a href="https://agentmods.dev/skills/caioribeiroclw-pixel/pluribus/context-receipts"><img src="https://agentmods.dev/badge/skills/caioribeiroclw-pixel/pluribus/context-receipts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,626 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.02626
Opus 5 $0.00016 $0.01313
Sonnet 5 $0.00007 $0.00525
Haiku 4.5 $0.00003 $0.00263

Measured 10d ago against content hash 6d268a5ceac4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

context-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 10d 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.

docs/.well-known/agent-skills/context-receipts/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context Receipts

Use this skill when an agent workflow claims to save context by selecting, deferring, hydrating, summarizing, compacting, pruning, delegating, attributing usage, or isolating context.

The job is not to log the private content. The job is to emit a small receipt that lets a reviewer answer:

what crossed the context boundary, what stayed out, and what audit gap remains?

Privacy defaults

Never include raw prompts, raw tool schemas, raw tool arguments, raw tool results, raw skill bodies, memory bodies, secrets, customer names, or full transcripts in the receipt.

Prefer:

  • stable ids or hashed ids;
  • counts and token/line buckets;
  • categorical reasons;
  • explicit booleans for raw content copied/not copied;
  • before/after context budget buckets;
  • an audit_gap field when the receipt proves routing but not semantic correctness.

60-second Tool Search smoke

For MCP Tool Search, lazy tool loading, or progressive disclosure, emit enough evidence to answer these seven checks:

  1. Index-only startup: did the session load a compact tool/server index instead of all full schemas?
  2. Search/routing: what hashed query/category or routing reason selected candidate tools?
  3. Hydration: which full tool definition was loaded, why, and how many definitions stayed suppressed?
  4. Call: which server/tool id was invoked, with argument/result redaction status and success/error status?
  5. Boundary: if a manager subagent or child agent was used, did raw child output return to the parent?
  6. Budget: what were the startup and post-hydration context-token buckets?
  7. Audit gap: what is not proven, such as whether the selected tool was semantically optimal?

Minimal JSONL event names:

{"event":"mcp.tool_index.loaded","loaded_server_count":12,"loaded_tool_index_count":84,"full_schema_count":0,"suppressed_tool_count":84,"raw_schema_copied":false,"startup_token_bucket":"lt_1k"}
{"event":"mcp.tool_search.performed","query_hash":"sha256:...","query_category":"repo_search","candidate_tool_count":5,"selected_tool_id":"github.search_code","raw_query_copied":false}
{"event":"mcp.tool_definition.loaded","tool_id":"github.search_code","hydrate_reason":"selected_after_tool_search","suppressed_tool_count":83,"definition_token_bucket":"1k_2k","raw_schema_copied":false}
{"event":"mcp.tool_call.completed","tool_id":"github.search_code","args_hash":"sha256:...","result_token_bucket":"2k_4k","raw_args_copied":false,"raw_result_copied":false,"status":"ok"}

Read the full file on GitHub · 207 lines

Changes

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.

  1. 10d ago First seen · 207 lines · 33 tokens per session scan A 6d268a5ceac4

Subscribe to this mod's changes

context-receipts is a skill published in the GitHub repository caioribeiroclw-pixel/pluribus (13 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 2,626 once invoked, about $0.0002 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.