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/terrene-foundation/metis/apigit clone --depth 1 https://github.com/terrene-foundation/metisWhat 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.00470 |
| Opus 5 | $0.00000 | $0.00235 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
api 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/api - Nexus Quick Reference
Purpose
Load the Nexus skill for zero-config multi-channel platform deployment (API + CLI + MCP simultaneously).
Step 0: Verify Project Uses Kailash Nexus
Before loading Nexus patterns, check that this project uses Kailash Nexus:
- Look for
kailash-nexusornexusinrequirements.txt,pyproject.toml - Look for
from nexus/import nexusin source files
If not found, inform the user: "This project doesn't appear to use Kailash Nexus. These patterns may not apply. Continue anyway?"
Quick Reference
| Command | Action |
|---|---|
/api |
Load Nexus patterns and deployment basics |
/api deploy |
Show deployment patterns |
/api session |
Show unified session management |
/api channels |
Show multi-channel configuration |
What You Get
- Zero-config deployment (API + CLI + MCP)
- Unified session management
- Workflow registration patterns
- Health monitoring
- Plugin system
Quick Pattern
from nexus import Nexus
app = Nexus()
# Register workflows
app.register(my_workflow)
# Deploy to all channels simultaneously
app.start() # API on :8000, CLI ready, MCP server running
Key Concepts
| Concept | Description |
|---|---|
| Unified Sessions | State maintained across API/CLI/MCP |
| Zero-Config | Automatic endpoint generation |
| Multi-Channel | Single workflow, multiple access methods |
| Plugin System | Extend with custom plugins |
Agent Teams
When working with Nexus, deploy:
- nexus-specialist — Multi-channel deployment, unified sessions, workflow registration
- release-specialist — Docker/Kubernetes production deployment
Related Commands
/sdk- Core SDK patterns/db- DataFlow database operations/ai- Kaizen AI agents/test- Testing strategies/validate- Project compliance checks
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 · 74 lines · 0 tokens per session scan A 283fe11bfd9f
api is a command published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 470 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.