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/prgit 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.00766 |
| Opus 5 | $0.00000 | $0.00383 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
pr 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Runbook: Pull Request
🌍 Language / 言語: English | 日本語
English
When to use
- when you need to prepare the minimum PR body and evidence set before requesting review
- when you need to decide whether to apply or reject review feedback and record the rationale
What to load (primary sources)
.github/pull_request_template.mddocs/ci/pr-automation.mddocs/ci-policy.mdpolicy/risk-policy.yml
Commands (copy/paste)
gh pr view "$PR_NUMBER" --json title,body,labels,reviewDecision,statusCheckRollup
gh api "repos/itdojp/ae-framework/pulls/${PR_NUMBER}/comments" --paginate
gh api "repos/itdojp/ae-framework/pulls/${PR_NUMBER}/reviews" --paginate
gh pr checks "$PR_NUMBER" --required
Artifacts to check
- the PR body, especially Rollback, Acceptance, and validation steps
- top-level review comments, inline replies, and thread resolution status
- the latest
policy-gate,gate, andverify-literesults
Escalation / follow-up
- if you intentionally do not apply a review suggestion, leave the reason in the PR thread or an explicit PR comment
- if
risk:highrequires extra human approvals, record the policy block and wait instead of overriding it - if required checks are blocked by unresolved AI review threads, resolve the threads first and then rerun or refresh the head branch
日本語
When to use
- review 依頼前に、PR 本文と evidence の最小セットを整えたいとき
- review 指摘を採用するか見送るかを判断し、根拠を残したいとき
What to load (primary sources)
.github/pull_request_template.mddocs/ci/pr-automation.mddocs/ci-policy.mdpolicy/risk-policy.yml
Commands (copy/paste)
gh pr view "$PR_NUMBER" --json title,body,labels,reviewDecision,statusCheckRollup
gh api "repos/itdojp/ae-framework/pulls/${PR_NUMBER}/comments" --paginate
gh api "repos/itdojp/ae-framework/pulls/${PR_NUMBER}/reviews" --paginate
gh pr checks "$PR_NUMBER" --required
Artifacts to check
- PR 本文、特に Rollback、Acceptance、検証手順
- review 本文、インライン返信、thread の解消状態
- 最新の
policy-gate、gate、verify-lite結果
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 · 93 lines · 0 tokens per session scan A 0c5f741fd78a
pr 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 766 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…