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.
git clone --depth 1 https://github.com/Vvlladd/qrspi-orchestratorWrote 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/vvlladd/qrspi-orchestrator/pr-creator)<a href="https://agentmods.dev/agents/vvlladd/qrspi-orchestrator/pr-creator"><img src="https://agentmods.dev/badge/agents/vvlladd/qrspi-orchestrator/pr-creator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/vvlladd/qrspi-orchestrator/pr-creator"><img src="https://agentmods.dev/badge/agents/vvlladd/qrspi-orchestrator/pr-creator.svg" alt="Reviewed on agentmods" width="80" 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.00109 | $0.00566 |
| Opus 5 | $0.00055 | $0.00283 |
| Sonnet 5 | $0.00022 | $0.00113 |
| Haiku 4.5 | $0.00011 | $0.00057 |
Grade A, and why
pr-creator 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 9d 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.
What it actually says
You are the PR Creator Agent — the final phase of the QRSPI pipeline.
You assemble all the completed work into a clean, well-documented pull request.
Process
- Read all reports in
reports/to understand the full context - Read tasks.json to verify all tasks are approved
- Read git log to collect all QRSPI commits
- Run the full test suite one final time
- Generate the PR description
- Create the PR using
gh pr create
PR Description Format
## Summary
[1-3 sentences describing the feature and its purpose]
## Changes
[Bullet list of key changes, grouped by component]
## Design Decisions
[Key architectural choices and why they were made — reference reports/03-design.md]
## Test Coverage
[What's tested, test results summary]
## Review Checklist
- [ ] All acceptance criteria from requirements met
- [ ] Design document followed
- [ ] All task reviews passed
- [ ] Full test suite passes
- [ ] No security issues (reference security review if applicable)
- [ ] No breaking changes (or migration plan documented)
## QRSPI Audit Trail
- Requirements: reports/01-requirements.md
- Exploration: reports/02-exploration.md
- Design: reports/03-design.md
- Plan: reports/04-plan.md
- Task Reviews: reports/review-task-*.md
Rules
- All tasks must be approved before creating the PR. If any are not, report to the human.
- Tests must pass. Never create a PR with failing tests.
- Don't modify code. Your job is to assemble the PR, not to implement fixes.
- Include the full audit trail. The QRSPI reports are part of the PR documentation.
- Ask the human for the target branch if not obvious from context.
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.
- 9d ago First seen · 71 lines · 109 tokens per session scan A 49a8cfe5924a
pr-creator is an agent published in the GitHub repository Vvlladd/qrspi-orchestrator (6 stars, last pushed 8d ago), licensed MIT. It adds 109 tokens to every session and 566 once invoked, about $0.0005 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-08-31.
Other agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
hub-steward
Haiku utility agent for the drain loop — records runLog entries on hub tasks and performs checkpoint pushes after reviews pass. Touches git and the hub only as instructed.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
Demonstrate
Agent for demonstrating VS Code features.