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/agents-doc-boundary-matrixgit clone --depth 1 https://github.com/itdojp/ae-frameworkWrote 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/agents/itdojp/ae-framework/agents-doc-boundary-matrix)<a href="https://agentmods.dev/agents/itdojp/ae-framework/agents-doc-boundary-matrix"><img src="https://agentmods.dev/badge/agents/itdojp/ae-framework/agents-doc-boundary-matrix.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.01793 |
| Opus 5 | $0.00000 | $0.00897 |
| Sonnet 5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade A, and why
agents-doc-boundary-matrix 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Documentation Boundary Matrix
🌍 Language / 言語: English | 日本語
English
Last updated: 2026-06-05
Purpose: define the ownership boundary that keeps AGENTS.md and docs/agents/* from duplicating primary-source policy text.
Boundary definitions (primary / secondary)
| Topic | Primary source (SSOT) | Secondary source (agent-facing route) | Managed scope |
|---|---|---|---|
| Overall CI policy | docs/ci-policy.md |
AGENTS.md, docs/agents/README.md |
required checks, opt-in controls, operating principles |
| CI operating procedure | docs/ci/ci-operations-handbook.md |
docs/agents/README.md |
daily monitoring, rerun, recovery procedure |
| CI incident recovery | docs/ci/ci-troubleshooting-guide.md |
AGENTS.md decision table |
failure classification and standard recovery flow |
| Claude Code entrypoint | docs/integrations/CLAUDE-CODE-TASK-TOOL-INTEGRATION.md, policy/risk-policy.yml |
CLAUDE.md, AGENTS.md, docs/agents/README.md |
Claude Code routing, handoff entrypoint, risk policy routing |
| Risk / label evaluation | policy/risk-policy.yml |
AGENTS.md invariants |
risk:low/high, required labels, gate conditions |
| Slash command implementation | .github/workflows/agent-commands.yml |
AGENTS.md, docs/agents/README.md |
accepted commands, attached labels, dispatch implementation |
| Workflow permission boundary | docs/ci/automation-permission-boundaries.md |
AGENTS.md progressive disclosure |
boundary between workflow_dispatch and issue_comment |
| PR automation operations | docs/ci/pr-automation.md |
AGENTS.md decision table |
review gate, auto-fix, auto-merge operations |
| Producer output artifact routing | docs/product/ASSURANCE-CONTROL-PLANE-POLICY.md, docs/agents/agent-producer-matrix.md, docs/agents/evidence-adapters.md, docs/reference/CONTRACT-CATALOG.md |
AGENTS.md, docs/agents/README.md |
producer boundary, raw output fixture mapping, normalized judgment artifacts |
| Multi-agent safety operations | docs/agents/multi-agent-safety.md |
AGENTS.md, docs/agents/README.md |
subagent permissions, ownership boundary, post-run checks |
| Dedicated worktree lifecycle | docs/maintenance/subagent-worktree-runbook.md |
docs/agents/multi-agent-safety.md |
worktree creation, isolation, integration, 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.
- 3d ago First seen · 81 lines · 0 tokens per session scan A bee1702664ad
agents-doc-boundary-matrix 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,793 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…