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/alphaaiservice/cortex/featuregit clone --depth 1 https://github.com/alphaaiservice/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.00026 | $0.01687 |
| Opus 5 | $0.00013 | $0.00843 |
| Sonnet 5 | $0.00005 | $0.00337 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
feature 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guided Feature Development
Build feature: $ARGUMENTS
Phase 0: Sprint Plan Integration
Before starting, check if this feature maps to a sprint task:
0. If $ARGUMENTS looks like a Jira issue key (matches ^[A-Z][A-Z0-9]+-\d+$, e.g. "PROJ-123"):
→ The `jira-integration` skill handles it: read the issue via the Atlassian MCP
server, use its summary + description + acceptance criteria as the feature spec,
and transition the issue to "In Progress". Then continue the flow below.
→ If Jira isn't connected, fall back to treating $ARGUMENTS as a plain description.
1. Check if SPRINT_PLAN.md exists
2. If $ARGUMENTS references a task ID (e.g., "task 2.3", "sprint task 2.3", or just "2.3"):
a. Read SPRINT_PLAN.md
b. Find the matching task
c. Verify its dependencies are completed (all blockedBy tasks are ✅)
d. If blocked: "⚠️ Task 2.3 is blocked by task 2.1 (not yet completed). Build task 2.1 first?"
e. If unblocked: Mark task as 🔄 (in progress) in SPRINT_PLAN.md
f. Use the task's description as the feature specification
3. If $ARGUMENTS is a description (not a task ID):
a. Search SPRINT_PLAN.md for a matching task by description similarity
b. If found: "Found matching sprint task 2.3. Linking this feature to it."
c. Mark as 🔄 in SPRINT_PLAN.md
4. If no SPRINT_PLAN.md exists: proceed normally without sprint tracking
Phase 1: Planning
SCOPE CHECK (CRITICAL): If the feature is too large (would touch 5+ files or take more than 2 hours), SPLIT it into micro-tasks first:
- Each micro-task = ONE file or ONE logical unit (max 2 hours)
- Present the split to the user: "This feature is large. I'll break it into X micro-tasks and build them one by one."
- Build each micro-task with its own commit
- This prevents context window exhaustion
- Understand the requirement — Parse the feature description (or sprint task spec)
- Explore existing code — Find related modules, patterns, and conventions
- Create a plan — Generate a step-by-step implementation plan:
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 · 190 lines · 26 tokens per session scan A 87de1685752b
feature is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 25d ago), licensed MIT. It adds 26 tokens to every session and 1,687 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-31.
Other commands, from other repositories
progress
Resumen operativo del proyecto: progreso, kanban, bloqueos y trazabilidad.
advisor
Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
card
Open one self-contained OverClick card.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.