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 commands/ibm-granite/granite.build/prgit clone --depth 1 https://github.com/ibm-granite/granite.buildWrote 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/commands/ibm-granite/granite.build/pr)<a href="https://agentmods.dev/commands/ibm-granite/granite.build/pr"><img src="https://agentmods.dev/badge/commands/ibm-granite/granite.build/pr.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.1 | $0.00014 | $0.01168 |
| Opus 5 | $0.00007 | $0.00584 |
| Sonnet 5 | $0.00003 | $0.00234 |
| Haiku 4.5 | $0.00001 | $0.00117 |
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR for granite.build
You are helping a developer create or update a pull request in the upstream repo (ibm-granite/granite.build) targeting the main branch. Follow these steps in order, stopping if any step fails.
Fork issue number (if provided): $ARGUMENTS
Step 0: Detect worktree context
-
Check if we are running inside a git worktree:
git rev-parse --is-inside-work-tree && git worktree list --porcelainIf the current directory is a secondary worktree (not the main working tree), note this — all git operations work normally from worktrees since they share remotes and history.
-
If
$ARGUMENTSis empty, try to auto-detect the issue number from the branch name:BRANCH=$(git branch --show-current)If
$BRANCHmatches the patternissue-<N>-*, extract<N>as the fork issue number. Inform the user:Auto-detected issue #N from branch name
<branch> -
Derive the fork owner:
FORK_OWNER=$(git remote get-url origin | sed -E 's|.*[:/]([^/]+)/.*|\1|')
Step 1: Pre-flight checks
- Confirm we are NOT on the
mainbranch — we should be on an issue branch - Run
git statusto check for uncommitted changes - If there are unstaged/uncommitted changes, ask the user whether to stage and commit them before proceeding. Always commit with
git commit -s(sign-off) — the upstream repo enforces the DCO check. - Check if a PR already exists for this branch:
Save the result — this determines whether we create or update.gh pr list --repo ibm-granite/granite.build --head "$FORK_OWNER":<current-branch-name> --state open --json number,url
Step 2: Format and lint (PR files only)
Only check files that will be in the PR — those changed between upstream/main and HEAD.
- Get the list of Python files changed in this PR:
git diff upstream/main...HEAD --name-only -- '*.py' - If there are Python files, run
isort --profile blackandblackon each file - If there are Python files, run
pylintandmypy --disable-error-code=import-untypeddirectly on each changed file - If linting produces errors, show them to the user and ask whether to fix them or proceed anyway
- If formatting changed any files, stage and commit them with
git commit -s -m "style: auto-format via pre-commit"(the-ssign-off is required by the upstream DCO check)
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 · 112 lines · 14 tokens per session scan A 59f6cc1edaff
pr is a command published in the GitHub repository ibm-granite/granite.build (44 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 1,168 once invoked, about $0.0001 per session on Opus 5. 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-09-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.