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 rjmurillo/ai-agents --skill context-gathergit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/context-gather)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/context-gather"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/context-gather/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/rjmurillo/ai-agents/context-gather"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/context-gather.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 134 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 135 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 136 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00086 | $0.01645 |
| Opus 5 | $0.00043 | $0.00822 |
| Sonnet 5 | $0.00017 | $0.00329 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade A, and why
context-gather 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Gather
Collect multi-source context before planning or implementation. Searches Serena, Context7, DeepWiki, and web sources, then returns a focused summary that downstream commands can detect and skip redundant fetches.
Model choice (behavior change from prior
/context-gatherslash command): this skill declaresmodel: claude-sonnet-4-6, downgraded from the slash command'sopus. Context retrieval is search-and-synthesis work, not deep reasoning; the cost-appropriate tier per ADR-002 model selection is sonnet. Skill behavior is otherwise unchanged.
Triggers
| Phrase | Context |
|---|---|
gather context for |
User requests pre-work context collection |
context-gather |
Direct skill invocation or programmatic call from build, plan, research commands (SPEC-005) |
what do we know about |
Exploratory context retrieval |
Quick Reference
| Field | Value |
|---|---|
| Input | Task description or technology topic (free text) |
| Output | Focused summary with code snippets, architectural insights, and CONTEXT_LOADED: <topic> marker |
| Quality Gate | Summary addresses the stated topic; at least one queried tier reconciled (short-circuit and early-stop exempt); marker line present |
When to Use
Use this skill when:
- Starting a complex task that needs multi-source context before planning or implementation.
- A lifecycle command (
/build,/plan,/research) triggers preflight context loading. - You need to pull framework-specific guidance from Context7 alongside project memory.
- Exploring what the memory tiers already record about a topic before committing to an approach.
When to Skip
Skip this skill when:
- A
CONTEXT_LOADED: <topic>marker for the same topic already exists in the current conversation. Do not re-fetch. - The task is trivial and single-step (no external context needed).
- You already have sufficient context from a prior skill invocation or manual research.
- The topic is purely internal to the current file (no cross-cutting concerns).
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 Changed · -2 lines · -1 tokens per session b55347eece94
- 4d ago Changed · -1 lines · -10 tokens per session 74a64d371437
- 6d ago First seen · 138 lines · 97 tokens per session scan A 73ed9f6423ee
context-gather is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,645 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
ci-cd
A guide for designing automated build and delivery workflows with GitHub Actions. These workflows can run checks such as tests, code-quality scans, coverage checks, and builds when code is pushed or a pull request is opened.
openclaw-control
A control interface for the OpenClaw AI assistant, covering messages, status checks, settings, and skill installation.
repository-readiness-eval
Evaluate a repository's readiness for AI-assisted development across 4 axes: code understanding, dependency restore, build success, and test execution. Use when onboarding to a new repo, assessing CI readiness, or validating that an AI agent can work effectively in a codebase.
deploy
Gated CI/CD pipeline management for GitHub Actions and GitLab CI, plus configuration review for other providers when their authenticated tooling is available. Use to set up or fix CI/CD.
loop-triage
Triage recent CI failures, open issues, and recent commits into a prioritized, actionable picture. Reads the prior STATE.md as memory and rewrites it. The maker half of the loop.
ci-triage
How to find out why a GitHub Actions run failed, and how to tell a real failure from a flake or an infrastructure problem. Use when a check is red, a workflow is stuck, or a run needs re-running.