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 technicalpickles/pickled-claude-plugins --skill checking-for-undisclosed-contextgit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWrote 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/technicalpickles/pickled-claude-plugins/checking-for-undisclosed-context)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/checking-for-undisclosed-context"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/checking-for-undisclosed-context/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/technicalpickles/pickled-claude-plugins/checking-for-undisclosed-context"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/checking-for-undisclosed-context.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.00000 | $0.01713 |
| Opus 5.5 | $0.00000 | $0.00685 |
| Sonnet 5.5 | $0.00000 | $0.00343 |
| Haiku 4.5 | $0.00000 | $0.00171 |
Grade A, and why
checking-for-undisclosed-context 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checking for Undisclosed Context
Overview
Text written by someone deep in a project accumulates vocabulary, acronyms, and structural assumptions from whatever they've been reading and discussing - a design doc, a ticket thread, an earlier stage of the same pipeline. None of that is visible to a reader who wasn't there. The author can't tell the difference between "this term is obvious" and "I only find this obvious because I wrote the doc it came from" without deliberately stepping outside their own head.
This skill is that step: read the text as a specific named reader, not as its author, and find the places where understanding it secretly depends on a document or conversation that reader was never given.
There's a second version of this specific to text that passes through multiple model turns, drafts, or agent hops: a model can coin a term on the spot to name something in the moment - a workaround, a state, a recurring shape - and that term gets carried into later output simply because it appeared once, not because anyone deliberately chose it as shared vocabulary. A few hops later, the turn that coined it is gone, and the term now reads as established shorthand to whoever encounters it next, even though nothing ever defined it and it may not exist anywhere else at all. This is the same leak as human-authored undisclosed context, but the "document the reader never saw" is a vanished conversation turn instead of a doc that at least still exists somewhere.
Different axis from writing-for-scannability (can the reader find the structure) and writing-voice (does it sound human). This is about access: could this specific reader actually follow it, or does it quietly assume a tab they don't have open.
When to use
- Reviewing a design doc, code-review prompt, PR/issue description, or subagent persona/prompt that's meant to stand alone
- Someone asks for a "cold read," or to check whether a doc is self-contained
- Writing something for a reader who explicitly hasn't seen the predecessor material - a follow-up proposal that shouldn't require the first one, a skill extracted out of a larger multi-stage protocol, a persona dispatched with a fresh context window
- Authoring a subagent prompt that has to work without inheriting the dispatching session's context
- Reviewing content that passed through multiple drafts, turns, or agent hops, where a term coined once earlier may have been carried forward as if it were established vocabulary
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.
- 1mo ago First seen · 56 lines · 0 tokens per session scan A e435d69a3bba
checking-for-undisclosed-context is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,713 tokens. 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-09-03.
Other skills, from other repositories
review-pubsub-subscriptions
Reviews Dapr pub/sub subscriptions and handlers in .NET and Python (declarative, programmatic, streaming) for CloudEvent handling, response statuses, idempotency, dead-letter handling and duplicate subscriptions. Use for "review my Dapr subscribers" or "check pub/sub handlers for idempotency".
review-agent-tools
Reviews agent tool implementations for idempotency, input validation, docstring quality and conventions. Use for "review agent tools" or "check tool idempotency".
review-workflow-management
Read-only audit of the HTTP management endpoints (start, status, terminate, pause, resume, raise-event, purge) an app exposes for Dapr Workflows, with DWF-MGT-NNN findings. Use for "review workflow management" or "check workflow HTTP endpoints". To operate runs on Diagrid Catalyst use the catalyst-ai plugin.
review-pubsub-components
Reviews Dapr pub/sub configuration (components, Subscription files, resiliency, dapr.yaml and Aspire wiring) for inline secrets, unsecured brokers, dead-letter topics without retry policies, scopes and app-id or port collisions. Use for "review my pub/sub components" or "audit Dapr pubsub YAML".
review-pubsub-publishing
Reviews Dapr pub/sub publishing code in .NET and Python for swallowed publish failures, wrong pub/sub names, content types, client lifetime, bulk-publish partial failures and payload size. Use for "review my pub/sub publishing code" or "audit Dapr publish calls".
review-agent-orchestration
Reviews multi-agent orchestration for pub/sub topic conventions, loop safety and handoff correctness. Use for "review agent orchestration" or "check multi-agent handoffs".