commands

A catalog of slash commands for pull requests and issues in GitHub, including commands for reviews, testing, security checks, performance checks, formal verification, and workflow dispatches.

In plain words
What is it for?
Use it to manage issues and pull requests with commands such as planning, assigning, reviewing, running quality or security checks, and marking work ready or done.
Why use it?
It gives teams a consistent set of commands for starting, reviewing, validating, blocking, and completing work. Some commands also apply predefined labels.

Agent

Install

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.

agentmods
npx agentmods add agents/itdojp/ae-framework/commands
Clone the repo
git clone --depth 1 https://github.com/itdojp/ae-framework
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 724 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00724
Opus 5 $0.00000 $0.00362
Sonnet 5 $0.00000 $0.00145
Haiku 4.5 $0.00000 $0.00072

Measured yesterday against content hash c695526e4441, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commands 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.

docs/agents/commands.md · 119 lines

What it actually says

Agent Commands Catalog

この文書は .github/workflows/agent-commands.yml から自動生成されます。手動編集しないでください。

PR向け Slash Commands

  • /blocking
  • /ci-fast-dispatch
  • /coverage
  • /enforce-a11y
  • /enforce-bdd-lint
  • /enforce-context-pack
  • /enforce-contracts
  • /enforce-coverage
  • /enforce-formal
  • /enforce-lh
  • /enforce-perf
  • /enforce-typecov
  • /formal-aggregate-dispatch
  • /formal-apalache-dispatch
  • /formal-help
  • /formal-quickstart
  • /formal-verify-dispatch
  • /handoff
  • /lh
  • /non-blocking
  • /perf
  • /pr-detailed
  • /pr-digest
  • /qa-batch-agents
  • /qa-batch-cli
  • /qa-batch-commands
  • /qa-batch-property
  • /ready
  • /review
  • /run-adapters
  • /run-cedar
  • /run-cedar-dispatch
  • /run-drift
  • /run-flake-dispatch
  • /run-formal
  • /run-hermetic
  • /run-qa
  • /run-qa-dispatch
  • /run-qa:agents
  • /run-qa:cli
  • /run-qa:commands
  • /run-qa:property
  • /run-resilience
  • /run-security
  • /run-security-dispatch
  • /run-spec
  • /spec-validation-dispatch
  • /verify-lite

Issue向け Slash Commands

  • /assign
  • /block
  • /done
  • /handoff
  • /plan
  • /ready-for-review
  • /start
  • /unblock

PRコマンドで付与される静的ラベル

  • ci-non-blocking
  • enforce-a11y
  • enforce-bdd-lint
  • enforce-context-pack
  • enforce-contracts
  • enforce-coverage
  • enforce-formal
  • enforce-lh
  • enforce-perf
  • enforce-typecov
  • pr-summary:detailed
  • pr-summary:digest
  • qa-batch:agents
  • qa-batch:cli
  • qa-batch:commands
  • qa-batch:property
  • run-adapters
  • run-cedar
  • run-drift
  • run-formal
  • run-hermetic
  • run-qa
  • run-resilience
  • run-security
  • run-spec

Issueコマンドで付与される静的ラベル

  • status:blocked
  • status:done
  • status:in-progress
  • status:review

動的ラベルパターン

  • coverage:<0-100>
  • handoff:agent-{a|b|c}
  • lh:<0-100>
  • perf:<0-100>

Source

  • .github/workflows/agent-commands.yml
Changes

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.

  1. yesterday First seen · 119 lines · 0 tokens per session scan A c695526e4441

Subscribe to this mod's changes

commands 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 724 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.

Related

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…

SigNoz/signoz · 0 tokens

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…

SigNoz/signoz · 0 tokens

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…

SigNoz/signoz · 0 tokens

codex

Production OpenAI-Codex-capable rootfs/initramfs.

the-void-ia/void-box · 0 tokens

claude

Production Claude-capable rootfs/initramfs.

the-void-ia/void-box · 0 tokens

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…

the-void-ia/void-box · 0 tokens