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/nafeesmansoor/codecortex/phase-statusgit clone --depth 1 https://github.com/NafeesMansoor/CodeCortexWhat 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.00246 |
| Opus 5 | $0.00000 | $0.00123 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
phase-status 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 25 lines · 0 tokens per session scan A 0eb36a480070
phase-status is a command published in the GitHub repository NafeesMansoor/CodeCortex (5 stars, last pushed yesterday), with no licence file. It costs nothing until one of its globs matches a file; then it loads 246 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-31.
Other commands, from other repositories
codesage-review
Review CodeSage feature slices in parallel and persist validated findings.
codesage-report
Render a Markdown findings report from .codesage/findings/. No LLM call — pure formatter.
codesage-revalidate
Re-check findings after code changes without inferring fixes from omission.
codesage-eval
Evaluate CodeSage effectiveness on a project by mining session-based eval cases and running the bench runner.
codesage-onboard
Onboard a project to CodeSage (global MCP registration, init, index, git hooks, agent hint).
codesage-reset
Drop a project's CodeSage index and rebuild from scratch (use after settings changes, device switches, or corruption).