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 agentmods add skills/rdudov/task-agent/context-discoverynpx skills add rdudov/task-agent --skill context-discoverygit clone --depth 1 https://github.com/rdudov/task-agentWhat 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 | $0.00039 | $0.00811 |
| Opus 5 | $0.00019 | $0.00405 |
| Sonnet 5 | $0.00008 | $0.00162 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
context-discovery 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 2d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Discovery
Scope
Use before broad search, live checks, or describing, justifying, or summarizing an already-made decision. A rule carries an outcome; the durable decision record carries its reasons.
Lookup Order
- Read the current task and tasks linked through
Parent TaskandRelated Tasks. - Run
skills/task-creator/scripts/tasks_index.py query --since 10d --format compact, or--search <term>when a keyword is known. The recent window includes every status and is the primary catalog;--status activeis only the secondary view for unfinished work. - For an indirect reference, open only useful recent candidates. Treat a
candidate excluded by the task's time or scope as no useful match; on no
useful match there, search all Markdown task artifacts below
tasks/, across the whole tree. The window is a reading order, not a search boundary.dateis the creation date, not when work finished: a task created three weeks ago and completed yesterday is outside--since 10d. - Read every relevant primary artifact that exists:
task.md,findings.md,verification.md, andsources.md. When a candidate describes or reproduces an observation made by another task, follow that provenance to the original task and read its primary artifacts before concluding. Record the concrete prior outcome that changes the current work, including an accepted repair or result identifier when the primary record provides one. - Read linked records under
data/projects/anddata/trips/, and the local repository/path indexes underdata/, whose formatdata/local-projects.example.mddescribes. For repository subsystems, read their decision records and usequery --project <record-name>for reverse lookup. - Read the target repository's agent instructions — root
AGENTS.mdand hidden ones such as.codex/or.claude/— plus its tool/runtime configuration, containers, and CI before review or implementation. Judge syntax, build, and convention questions against the runtime that repository declares rather than remembered defaults; when a construct looks wrong but the declared runtime makes it valid, record the runtime-context gap instead of reporting breakage. - Search sibling repositories only after durable local context is exhausted.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 72 lines · 39 tokens per session scan A b157a403ed07
context-discovery is a skill published in the GitHub repository rdudov/task-agent (4 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 811 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…