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/specgit 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.00645 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
spec 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.
What it actually says
Agents Runbook: Spec
🌍 Language / 言語: English | 日本語
English
When to use
- when you need to verify consistency and code generation drift after changing spec files
- when you need to fix a spec validation failure with the smallest possible local scope
What to load (primary sources)
docs/spec/context-pack.mddocs/quality/issue-requirements-traceability.mdscripts/spec/*.github/workflows/spec-validation.yml
Commands (copy/paste)
pnpm -s run spec:lint
pnpm -s run spec:validate
pnpm -s run validate:specs:ci
pnpm -s run spec:codegen
Artifacts to check
artifacts/spec/*tests/golden/snapshots/*- PR results for Spec Validation and Code Generation
Escalation / follow-up
- if the spec change is broad, split generated diffs and manual edits into separate PRs when possible
- if the change breaks schema compatibility, record the migration path in the PR body before requesting review
- if
spec:codegenrewrites unrelated files, identify the generating source first and avoid mixing drift cleanup with semantic changes
日本語
When to use
- spec file 変更後に整合性と code generation drift を確認したいとき
- Spec validation の失敗を最小の局所修正で直したいとき
What to load (primary sources)
docs/spec/context-pack.mddocs/quality/issue-requirements-traceability.mdscripts/spec/*.github/workflows/spec-validation.yml
Commands (copy/paste)
pnpm -s run spec:lint
pnpm -s run spec:validate
pnpm -s run validate:specs:ci
pnpm -s run spec:codegen
Artifacts to check
artifacts/spec/*tests/golden/snapshots/*- PR 上の Spec Validation と Code Generation の結果
Escalation / follow-up
- spec 変更が広範囲な場合は、生成差分と手動編集差分を分けて、可能な限り PR を分割する
- schema compatibility を壊す変更は、review 依頼前に移行方針を PR 本文へ明記する
spec:codegenが無関係なファイルまで書き換える場合は、まず生成元を特定し、drift cleanup と意味変更を混在させない
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 · 92 lines · 0 tokens per session scan A 8eaedb4635f4
spec 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 645 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…