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 agents/igrechuhin/cortex/implement-codegit clone --depth 1 https://github.com/igrechuhin/CortexWhat 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.00063 | $0.00897 |
| Opus 5 | $0.00032 | $0.00449 |
| Sonnet 5 | $0.00013 | $0.00179 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
implement-code 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 yesterday.
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.
What it actually says
Implement all remaining plan subtasks; run quality gate after each; write result.
- Load context: call
mcp__cortex__pipeline_handoff(operation="read", pipeline="implement", phase="code"). Ifplan_filepresent, derive slug and readcortex://contextandcortex://rules. Skip subtasks listed inpartial_progress. - Scope: use
mcp__cortex__think()to enumerate remaining subtasks and estimate scope. Implement as many consecutive subtasks as context allows (stop only on 3× gate failure or <20% context remaining). - Implement each subtask:
- Follow rules from
cortex://rules. Use dependency injection. Add# BELIEF:before dict-key/attribute-chain access on external data. - Write tests alongside code (AAA pattern). Re-read each file after editing to confirm change applied. Grep for existing helper function definitions before creating new ones to avoid duplicates.
- Incremental validation: after each refactor, run type and quality checks — do not batch changes.
- Duplicate-definition search: before modifying a function, search for all definitions of that name.
- Drift check: if
.cortex/.session/session-goal.mdexists and edit is out of scope, emit[DRIFT WARNING: <path> — <reason>].
- Follow rules from
- Quality gate after each subtask: call
mcp__cortex__run_quality_gate(). Ifpreflight_passed: false, callmcp__cortex__autofix()then retry (max 3 iterations). Gate must pass before moving to next subtask.- No-progress check (before each retry): append
{"target":"<subtask file/module>","outcome_signature":"<error type + message shape, no line numbers/timestamps>","attempt_number":<n>}to this phase'sattempt_historylist (read prior list viamcp__cortex__pipeline_handoff(operation="read", pipeline="implement", phase="code"), append, write full list back viaoperation="write"). If the last 3 records share the sametargetand identicaloutcome_signature, this is a task-level no-progress trip — distinct from the MCP circuit breaker (shared-conventions.md): STOP retrying this subtask, writestatus:"failed",step_fully_complete:false, and report: "No-progress monitor tripped after 3 consecutive attempts with identical outcome on target ''. Pausing for orchestrator re-plan/human check-in." Do not attempt a 4th iteration on this subtask.
- No-progress check (before each retry): append
- Write result via
mcp__cortex__pipeline_handoff(operation="write", pipeline="implement", phase="code", ...):
{"status":"passed|failed","subtask":"<all subtasks completed this invocation>","files_changed":["..."],"tests_added":<n>,"coverage":<value>,"step_fully_complete":true|false,"fix_iterations":<n>}
Set step_fully_complete:true only when all plan steps are done (not in partial_progress and not remaining).
Report (compact): Subtasks done / remaining · Files changed · Tests added <n> · Coverage <n>% · Gate ✅/❌ · Fully complete yes/no
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.
- yesterday First seen · 31 lines · 63 tokens per session scan A f4aee34b442e
implement-code is an agent published in the GitHub repository igrechuhin/Cortex (3 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 897 once invoked, about $0.0003 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 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.