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/igoroliveirg/prometheus/_context-loadergit clone --depth 1 https://github.com/igoroliveirg/prometheusWhat 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.02285 |
| Opus 5 | $0.00000 | $0.01143 |
| Sonnet 5 | $0.00000 | $0.00457 |
| Haiku 4.5 | $0.00000 | $0.00229 |
Grade A, and why
_context-loader 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Activation Protocol
Load only what you need. Every file read costs tokens -- earn each one.
Multi-Project Path Resolution
Prometheus supports multiple projects. Memory and profiles are project-specific.
How to resolve paths:
- Detect the current working directory from the conversation context
- Map it to a project path:
~/.claude/projects/-{cwd-with-dashes}/- Example:
/Users/user/Desktop/pitaia→~/.claude/projects/-Users-user-Desktop-pitaia/ - Example:
/Users/user/Desktop/Base Viral→~/.claude/projects/-Users-user-Desktop-Base-Viral/
- Example:
- Load files from the project-specific path first, then fall back to global
~/.claude/
Path resolution table:
| Reference in commands | Resolves to (project-specific) | Fallback (global) |
|---|---|---|
memory/stack.md |
~/.claude/projects/{project}/memory/stack.md |
~/.claude/memory/stack.md |
memory/decisions.md |
~/.claude/projects/{project}/memory/decisions.md |
~/.claude/memory/decisions.md |
memory/conventions.md |
~/.claude/projects/{project}/memory/conventions.md |
~/.claude/memory/conventions.md |
memory/gotchas.md |
~/.claude/projects/{project}/memory/gotchas.md |
~/.claude/memory/gotchas.md |
profile.md |
~/.claude/projects/{project}/profile.md |
~/.claude/profiles/active.md |
state/current.md |
~/.claude/projects/{project}/state/current.md |
~/.claude/state/current.md |
state/history/ |
~/.claude/projects/{project}/state/history/ |
~/.claude/state/history/ |
Always global (never project-specific):
~/.claude/global-memory/*— Cross-project knowledge~/.claude/commands/*— Agent commands~/.claude/hooks/*— Enforcement hooks~/.claude/playbooks/*— Workflow playbooks~/.claude/inbox/*— Agent inboxes
Always (every activation)
- Check inbox:
~/.claude/inbox/[your-agent-name].md-- skip if empty or missing Inbox Read Validation: If inbox has messages withStatus: unread, you MUST read and acknowledge them before proceeding. Unread messages may contain critical handoff context, blockers, or priority changes. Skipping inbox is a pipeline violation. - Check state: project-specific
~/.claude/projects/{project}/state/current.md(fall back to~/.claude/state/current.mdif project-specific doesn't exist) -- resume if an active session exists for you; accept any pending handoff - Greet with status summary -- report inbox messages, active story/state, and readiness
- Log activation: Append a row to
~/.claude/logs/audit.md:| {ISO timestamp} | {your-agent-name} | activated | Session start | - Reset tool counter: Write
0to~/.claude/state/.tool-count - Update activation metric: In
~/.claude/metrics/dashboard.md, increment your agent's Activations count in the Agent Activity table by 1, and increment the "Agent Activations" value in the Workflow table by 1
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 · 184 lines · 0 tokens per session scan A 0aa24aea4f85
_context-loader is a command published in the GitHub repository igoroliveirg/prometheus (3 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,285 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.