Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add knitli/toolshed/plugin install ctxWrote 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/commands/knitli/toolshed/ctx-discover)<a href="https://agentmods.dev/commands/knitli/toolshed/ctx-discover"><img src="https://agentmods.dev/badge/commands/knitli/toolshed/ctx-discover/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/commands/knitli/toolshed/ctx-discover"><img src="https://agentmods.dev/badge/commands/knitli/toolshed/ctx-discover.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.00012 | $0.00656 |
| Opus 5.5 | $0.00005 | $0.00262 |
| Sonnet 5.5 | $0.00002 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
ctx-discover 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ctx:discover — Context File Inventory
Scan this repository and produce a complete inventory of AI context files across all tool ecosystems.
Arguments
$ARGUMENTS
- No arguments: discover all context files across all ecosystems.
- Ecosystem names (e.g.,
/ctx:discover cursor serena): restrict scanning to those ecosystems only. - Directory paths (e.g.,
/ctx:discover .claude/ .serena/): scan only those directories.
Instructions
Search every location listed in the plugin's authoritative ecosystem inventory. If the user provided arguments above, restrict the scan to the specified ecosystems or directories. For each file found, record its path, which tool ecosystem it belongs to, its type (memory, config, planning, or output), file size, and last-modified date.
Locations to scan
The authoritative list of known ecosystems, root files, nested memory files, tool directories, config files, and ignore directories lives in ${CLAUDE_PLUGIN_ROOT}/data/context-files.ini. Read that file first — it is the single source of truth. Any file, directory, or glob listed there is in scope; anything not listed is not. When adding support for a new ecosystem, add it to the INI, not here.
Briefly, the INI covers ~15 ecosystems including Claude Code, universal AGENTS.md, Gemini, OpenAI Codex, Cursor, Windsurf, Continue, Roo/Cline, Crush, Aider, Serena, spec-kit, GitHub agents/skills, VS Code, and planning/output directories (claudedocs/, specs/, plans/, etc.). The [ignore] section lists directories the scanner must not descend into (.git, node_modules, .venv, build outputs). The [heuristics] section lists standard ALL_CAPS markdown filenames to exclude from heuristic detection.
Heuristic detection (not covered by the INI's exact-match entries): after reading the INI and collecting its listed files, also scan for:
- Markdown files in the repo root with ALL_CAPS names that don't match the
allcaps_excludelist in[heuristics]. These are often context files in disguise. - Symlinks between any context files (e.g.,
GEMINI.md → CLAUDE.md). - Files in
docs/that appear AI-agent-targeted (phrases like "project overview", "when working with this repo", "assistant instructions") rather than user-facing.
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 · 42 lines · 12 tokens per session scan A 2814f7869656
ctx-discover is a command published in the GitHub repository knitli/toolshed (1 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 656 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
skillrx
Scan AI agent plugin or skill for malicious patterns before install.
memory-compact
Run a dry run first.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.