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 skills/nickcrew/claude-cortex/claude-consultnpx skills add NickCrew/Claude-Cortex --skill claude-consultgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nickcrew/claude-cortex/claude-consult)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/claude-consult"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/claude-consult.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00070 | $0.02129 |
| Opus 5 | $0.00035 | $0.01064 |
| Sonnet 5 | $0.00014 | $0.00426 |
| Haiku 4.5 | $0.00007 | $0.00213 |
Grade A, and why
claude-consult 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Consult
Get expert help from Claude specialist agents during implementation. Each agent has domain-specific skills pre-loaded and tools scoped to its role.
This is NOT a replacement for the review gates. The agent-loops skill
defines formal code review (specialist-review) and test audit
(diff-test-audit) gates that run after implementation. This skill is for
asking questions during implementation — before you've written code, while
you're writing it, or when you're stuck.
When to Use
- "How does this module work?" — before implementing
- "Does my approach match existing conventions?" — while implementing
- "Is this pattern secure?" — before committing to a design
- "Why is this test failing?" — when stuck
- "What do the testing standards say about X?" — before writing tests
- "Is this component accessible?" — during UI work
How to Invoke
claude -p --agent <agent-name> "<your question>"
All agents run headless (-p / print mode). They read the codebase, apply their
loaded skills, and return an answer to stdout. Capture or pipe as needed:
# Direct invocation
claude -p --agent debugger "Why is test_auth_flow failing in src/auth/tests.py?"
# Capture to variable
ANSWER=$(claude -p --agent security-auditor "Is the input validation in src/api/handler.py safe?")
# Save to file
claude -p --agent architect-reviewer "Does adding a cache layer between api and db match the existing architecture?" > /tmp/arch-advice.md
Agent Roster
Codebase Understanding
| Agent | Use when you need to... | Skills loaded |
|---|---|---|
search-specialist |
Find where something is defined or called | codanna-codebase-intelligence |
architect-reviewer |
Evaluate module boundaries and dependencies | system-design, api-design-patterns |
docs-architect |
Understand existing documentation structure | documentation-production, code-explanation |
Code Quality & Patterns
| Agent | Use when you need to... | Skills loaded |
|---|---|---|
code-reviewer |
Check if code follows project conventions | code-quality-workflow, testing-anti-patterns, secure-coding-practices |
refiner |
Get suggestions for improving code quality | code-quality-workflow |
rest-expert |
Design or check REST API patterns | api-design-patterns |
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 · 206 lines · 70 tokens per session scan A e8f71384eb43
claude-consult is a skill published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 2,129 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-09-03.
Other skills, from other repositories
performance-smell-detection
Detect potential code-level performance smells in Java - streams, collections, boxing, regex, object creation. Provides awareness, not absolutes - always measure before optimizing. For JPA/database performance, use jpa-patterns instead.
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
debug
Systematically diagnose and resolve bugs through conversational investigation and root cause analysis.
analyze-kernel-bottleneck
Systematically identify whether a GPU kernel is compute-bound, memory-bound, or latency-bound using roofline analysis, occupancy calculations, compute/load ratio per tile, and SASS instruction inspection. Produces a decision matrix for optimization strategy selection (cp.async, warp interleaving, tiling…
chrysopoeia
Extract maximum value from existing code — performance optimization, API surface refinement, and dead weight elimination. The art of turning base code into gold through systematic identification and amplification of value-bearing patterns. Use when optimizing a working but sluggish codebase, refining an API surface…
conduct-post-mortem
Conduct a blameless post-mortem analysis after an incident. Build timeline reconstruction, identify contributing factors, and generate actionable improvements. Focus on systemic issues rather than individual blame. Use after any production incident or service degradation, following a near-miss, when investigating…