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 agents/itdojp/ae-framework/context-packgit clone --depth 1 https://github.com/itdojp/ae-frameworkWhat 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.01814 |
| Opus 5 | $0.00000 | $0.00907 |
| Sonnet 5 | $0.00000 | $0.00363 |
| Haiku 4.5 | $0.00000 | $0.00181 |
Grade A, and why
context-pack 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Runbook: Context Pack
🌍 Language / 言語: English | 日本語
English
When to use
- when you need to run Context Pack structure validation or Phase5+ validation
- when you need to verify consistency between Context Pack and Discovery Pack while
upstream_refsare present - when you need to recover from Boundary Map, dependency boundary, or
verify:litefailures
What to load (primary sources)
docs/spec/context-pack.mddocs/guides/context-pack-onboarding-checklist.mddocs/guides/upstream-context-promotion.mddocs/operations/context-pack-troubleshooting.md
Commands (copy/paste)
The commands below are the current operator baseline. Start with the focused validator, then re-run verify:lite.
pnpm -s run context-pack:validate
pnpm -s run context-pack:validate -- --discovery-pack "spec/discovery-pack/**/*.{yml,yaml,json}"
pnpm -s run context-pack:verify-functor
pnpm -s run context-pack:verify-natural-transformation
pnpm -s run context-pack:verify-product-coproduct
pnpm -s run context-pack:verify-boundary-map
pnpm -s run context-pack:verify-phase5
pnpm -s run context-pack:deps
pnpm -s run context-pack:e2e-fixture
node scripts/context-pack/suggest.mjs --report-dir artifacts/context-pack
pnpm -s run verify:lite
Artifacts to check
artifacts/context-pack/context-pack-phase5-report.{json,md}artifacts/context-pack/context-pack-validate-report.{json,md}artifacts/context-pack/context-pack-functor-report.{json,md}artifacts/context-pack/context-pack-natural-transformation-report.{json,md}artifacts/context-pack/context-pack-product-coproduct-report.{json,md}artifacts/context-pack/context-pack-boundary-map-report.{json,md}artifacts/context-pack/deps-summary.{json,md}artifacts/context-pack/context-pack-suggestions.{json,md}artifacts/verify-lite/verify-lite-run-summary.json- CI job results for
context-pack-e2e,verify-lite, and the Context Pack validators
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 · 202 lines · 0 tokens per session scan A 0b8fcfc60c9b
context-pack is an agent published in the GitHub repository itdojp/ae-framework (2 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,814 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 agents, from other repositories
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
playwright-test-healer
Use this agent to debug and fix failing SigNoz E2E Playwright tests. Examples — Context: A spec is red. user: 'tests/e2e/tests/dashboards/list.spec.ts is failing, fix it' assistant: 'Using the healer agent to debug each failing scenario and adjust the spec.' Context: After a frontend change a previously-green spec…
playwright-test-planner
Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…
codex
Production OpenAI-Codex-capable rootfs/initramfs.
claude
Production Claude-capable rootfs/initramfs.
doc-style
Markdown documentation prose — RFCs, ADRs, files under docs/, and READMEs — follows the same one-paragraph-per-line rule as commit messages. Write each paragraph on a single line; do not hard-wrap prose to a fixed column. The renderer reflows it to the reader's display width, whereas manual mid-paragraph line breaks…