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/cdeust/cortex/methodologygit clone --depth 1 https://github.com/cdeust/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.00011 | $0.00183 |
| Opus 5 | $0.00005 | $0.00092 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
methodology 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
Use the methodology-agent:query_methodology tool with the current working directory to retrieve the user's cognitive profile for this domain.
Display the context field as a summary paragraph, then offer:
- Run
methodology-agent:rebuild_profilesif the profile seems stale or the user wants a fresh analysis - Run
methodology-agent:list_domainsto show all detected domains - If the companion cortex-viz MCP is installed, run its
get_methodology_graphtool for visualization data (it was extracted from Cortex in v3.21.0 and is not part of this server)
If no profile exists yet, run methodology-agent:rebuild_profiles first to build one from session history.
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 · 14 lines · 11 tokens per session scan A 714cdc8cf354
methodology is a command published in the GitHub repository cdeust/Cortex (71 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 183 once invoked, about $0.0001 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-30.
Other commands, from other repositories
brief
Command "brief" from csmar432/finai-research, covering brief — 生成研究简报, arguments, 描述, 工作方式 and 示例.
validate-dependencies
Validate all task dependencies for issues.
flow-nexus-neural
Train and deploy neural networks in distributed sandboxes.
flow-nexus-auth
Flow Nexus authentication and user management.
validate-prd
Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality.
editorial-review-structure
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension.