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/philngt/contextd/contextd-export-manifestgit clone --depth 1 https://github.com/philngt/contextdWrote 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/commands/philngt/contextd/contextd-export-manifest)<a href="https://agentmods.dev/commands/philngt/contextd/contextd-export-manifest"><img src="https://agentmods.dev/badge/commands/philngt/contextd/contextd-export-manifest.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 | $0.00000 | $0.00352 |
| Opus 5 | $0.00000 | $0.00176 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
contextd-export-manifest 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 4d 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.
What it actually says
Export Manifest
Generate .contextd/manifest.json from canonical sources (.claude/commands/*.md, .claude/agents/*.md, packs/*/pack.yaml, agents/pipeline/*.md).
/contextd-export-manifest [--dry-run]
| Flag | Description |
|---|---|
--dry-run |
Print manifest to stdout without writing file |
Behavior
- Parse
.claude/commands/*.md→ extract title from first H1. - Parse
.claude/agents/*.md→ extract YAML frontmatter (name,description,tools,model). - Parse
packs/*/pack.yaml→ name, version, description, components. - Parse
agents/pipeline/*.md→ pipeline doc index. - Write
.contextd/manifest.json(or print if--dry-run).
Manifest is a generated index, not single source of truth. Canonical content remains in the markdown files it references.
Verification
After running, confirm counts match:
python scripts/generate_manifest.py --dry-run | python -c "
import json, sys
d = json.load(sys.stdin)
print(f'commands={len(d[\"commands\"])} agents={len(d[\"agents\"])} packs={len(d[\"packs\"])}')
"
Counts should match:
commands== number of.claude/commands/*.mdfiles (excludingREADME.md)agents== number of.claude/agents/*.mdfilespacks== number ofpacks/*/directories withpack.yaml
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.
- 4d ago First seen · 43 lines · 0 tokens per session scan A a178595551fd
contextd-export-manifest is a command published in the GitHub repository philngt/contextd (29 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 352 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-30.
Other commands, from other repositories
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
reclaim-knowledge
Organize scattered professional material into a domain-based second-brain architecture. Maps existing sources (Canva, Drive, local folders, Notion, screenshots) to functional domains. Non-technical-friendly — produces folder structure + drag-and-drop instructions, not CLI commands.
orchestrate-brain
Weekly 30-minute second-brain review ritual. Orchestrates inbox clear, lightweight distillation, vault maintenance, cross-reference pass, and next-week capture focus. The compounding rhythm that keeps the system alive.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.