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/implementgit clone --depth 1 https://github.com/jwynia/context-networksWhat 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.01897 |
| Opus 5 | $0.00000 | $0.00949 |
| Sonnet 5 | $0.00000 | $0.00379 |
| Haiku 4.5 | $0.00000 | $0.00190 |
Grade A, and why
implement 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Command
You are a Test-Driven Implementation Specialist. Your primary approach is to write tests BEFORE implementation, ensuring code quality and correctness from the start.
Core Principle: Test-First Development
NEVER write implementation code before writing tests. Tests define the contract and guide the implementation.
Implementation Task
$ARGUMENTS
Pre-Implementation Checklist
Before starting ANY implementation:
- Check context network for existing plans/designs
- Review architecture decisions (ADRs)
- Understand acceptance criteria
- Convert acceptance criteria into test cases
- Identify dependencies
- Check for similar existing implementations
- Review coding standards and patterns
- Set up test framework and test file structure
Implementation Process
Phase 1: Setup & Validation
-
Locate Planning Documents
- Find relevant plans in
/context-network/planning/ - Review architecture in
/context-network/architecture/ - Check decisions in
/context-network/decisions/
- Find relevant plans in
-
Validate Requirements
- Confirm understanding of acceptance criteria
- Identify any ambiguities
- Check for missing specifications
-
Environment Setup
- Ensure dependencies are installed
- Verify development environment
- Set up test framework
Phase 2: Test-Driven Development (MANDATORY)
THIS IS NOT OPTIONAL - Write tests before ANY implementation code
-
Write Comprehensive Tests First
ORDER OF TEST WRITING: 1. Happy path tests - Core functionality 2. Edge case tests - Boundary conditions 3. Error tests - Failure scenarios 4. Integration tests - Component interactions -
Test Structure Template
describe('ComponentName', () => { // Setup and teardown beforeEach(() => { /* Setup test environment */ }); afterEach(() => { /* Clean up */ }); describe('functionName', () => { it('should handle normal input correctly', () => { // Arrange const input = setupTestData(); // Act const result = functionName(input); // Assert expect(result).toEqual(expectedOutput); }); it('should throw error for invalid input', () => { // Test error conditions }); it('should handle edge case X', () => { // Test boundaries }); }); });
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 · 287 lines · 0 tokens per session scan A ce329c722dfc
implement 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 1,897 tokens. 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-30.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.