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 commands/jwynia/context-networks/researchgit clone --depth 1 https://github.com/jwynia/context-networksWrote 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/jwynia/context-networks/research)<a href="https://agentmods.dev/commands/jwynia/context-networks/research"><img src="https://agentmods.dev/badge/commands/jwynia/context-networks/research.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 | $0.00000 | $0.02824 |
| Opus 5 | $0.00000 | $0.01412 |
| Sonnet 5 | $0.00000 | $0.00565 |
| Haiku 4.5 | $0.00000 | $0.00282 |
Grade B, and why
research scanned grade B with 1 finding 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 4d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
## Output Instructions How it starts
The opening of the file, as written. The whole thing — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Integration Context Network Agent Prompt
Task Context
You are conducting research using the Research MCP server on the topic: $ARGUMENTS
Your goal is to perform comprehensive research and integrate all findings, analysis, and insights into the context network following proper organizational principles.
Critical Domain Boundary
REMEMBER: All research outputs, analysis documents, and synthesis reports MUST be placed in the context network, NOT in the project root. Only implementation artifacts belong outside the context network.
Research Execution Process
Phase 1: Research Planning & Context Discovery
-
Parse Research Scope
Topic: $ARGUMENTS- Identify key concepts and domains to explore
- Determine research depth needed (exploratory vs. deep dive)
- List specific questions to answer
-
Context Network Reconnaissance
- Search existing context network for related research
- Check discovery records for related insights (
/discoveries/records/) - Review learning paths for context evolution (
/learning-paths/) - Identify relevant domain nodes
- Map existing knowledge to avoid duplication
- Note gaps the research should fill
-
Research Strategy
- Define search queries for Research MCP
- Plan research phases (broad → specific)
- Set criteria for source evaluation
- Establish synthesis approach
- Create a research report file named with the freshly verified current date and topic in the context network.
Phase 2: Research Execution
-
Initial Broad Research
mcp.research("$ARGUMENTS overview current state") mcp.research("$ARGUMENTS key concepts definitions") mcp.research("$ARGUMENTS major approaches methods") -
Domain-Specific Deep Dives Based on initial findings, explore specific aspects:
- Technical implementations
- Theoretical foundations
- Practical applications
- Case studies/examples
- Limitations/challenges
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.
- 4d ago First seen · 394 lines · 0 tokens per session scan B 9468a314fbe2
research is a command published in the GitHub repository jwynia/context-networks (24 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,824 tokens. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.