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/callstackincubator/rozenite/pull-requestsgit clone --depth 1 https://github.com/callstackincubator/rozeniteWhat 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.00466 |
| Opus 5 | $0.00000 | $0.00233 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
pull-requests 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 today.
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull requests
Read this guide before preparing or opening a pull request.
Before opening
-
Ensure the branch addresses one focused change; if it spans multiple unrelated types of change (e.g. a feature plus an unrelated refactor), split it into separate pull requests.
-
Add a version plan when the change affects a publishable package's behavior; see
docs/agents/version-plans.md. -
Update the relevant package or
website/documentation if the change adds or alters user-facing behavior. -
Run and report validation proportionate to the change. From the repository root, after making sure the base branch ref is present locally:
git fetch origin main pnpm checks:affected && pnpm test:affected--affectedneeds that ref to diff against; without it Turborepo treats every package as affected and rebuilds the whole monorepo. Reach for the:allvariants only when the change is genuinely repo-wide, such as a release or an edit to a root config file. Seedocs/agents/validation.md. -
Ensure the pull request title follows Conventional Commits (e.g.
feat(redux-devtools): add some new feature) — it becomes the squash commit title and scope should match the package name.
Description
Fill in .github/pull_request_template.md as-is; do not replace or rename its
sections. Write for the reviewer and for the person affected by the change:
- Description — what changed, in plain terms.
- Related Issue — link the open issue this addresses; this repository
only accepts pull requests tied to one (see
CONTRIBUTING.md). - Context — why this approach was chosen and anything a reviewer needs to know before reviewing.
- Testing — how the change was verified (commands run, playground steps, manual checks).
Do not add extra sections (rollout notes, generated-by footers, etc.) beyond the template unless the change specifically calls for it.
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.
- today First seen · 46 lines · 0 tokens per session scan A 9c97b9f9e92f
pull-requests is an agent published in the GitHub repository callstackincubator/rozenite (653 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 466 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
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
worktree-collaboration
This document defines the default collaboration protocol for multiple Agents working on Vibelution in parallel.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
issue-tracker
Predict issues and PRDs live in Consensys Jira.
domain
This document defines the canonical domain language for Vibelution so architecture work can use stable names for the same concepts. It is intentionally small: add terms when they become load-bearing in design or tests.
sdd-planner
Breaks a feature spec + design into atomic, ordered, testable tasks. Use AFTER spec.md and design.md exist and AFTER the researcher's report. Writes specs/ /tasks.md. Stack-agnostic.