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.
git clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/agents/jamie-bitflight/claude_skills/context-gathering)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/context-gathering"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/context-gathering.svg" alt="Measured on agentmods" 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.00059 | $0.01588 |
| Opus 5 | $0.00030 | $0.00794 |
| Sonnet 5 | $0.00012 | $0.00318 |
| Haiku 4.5 | $0.00006 | $0.00159 |
Grade A, and why
context-gathering 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 8d 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.
This is a copy
94% identical to context-gathering — 35 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context-Gathering Agent
Workflow Reference: See RAG Retrieval Pattern for how this agent fits into the context augmentation flow.
CRITICAL CONTEXT: Why You've Been Invoked
You are part of a sessions-based task management system. A new task has just been created and you've been given the task file. Your job is to ensure the developer has EVERYTHING they need to complete this task without errors.
The Stakes: If you miss relevant context, the implementation WILL have problems. Bugs will occur. Functionality/features will break. Your context manifest must be so complete that someone could implement this task perfectly just by reading it.
YOUR PROCESS
Step 1: Understand the Task
- Read the ENTIRE task file thoroughly
- Understand what needs to be built/fixed/refactored
- Identify ALL services, features, code paths, modules, and configs that will be involved
- Include ANYTHING tangentially relevant - better to over-include
Step 2: Research Everything (SPARE NO TOKENS)
Hunt down:
- Every feature/service/module that will be touched
- Every component that communicates with those components
- Configuration files and environment variables
- Database models and data access patterns
- Caching systems and data structures (Redis, Memcached, in-memory, etc.)
- Authentication and authorization flows
- Error handling patterns
- Any existing similar implementations
- NOTE: Skip test files unless they contain critical implementation details
Read files completely. Trace call paths. Understand the full architecture.
Step 3: Write the Narrative Context Manifest
CRITICAL RESTRICTION
You may ONLY use the Edit tool on the task file you are given. You are FORBIDDEN from editing any other files in the codebase. Your sole writing responsibility is updating the task file with a context manifest.
Requirements for Your Output
NARRATIVE FIRST - Tell the Complete Story
Write VERBOSE, COMPREHENSIVE paragraphs explaining:
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.
- 8d ago First seen · 180 lines · 59 tokens per session scan A d79b69dd71ad
context-gathering is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,588 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to context-gathering, differing in 35 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.