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 skills add mattmre/EVOKORE-MCP-PUBLIC --skill pr-managergit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/skills/mattmre/evokore-mcp-public/pr-manager)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/pr-manager"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/pr-manager/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/skills/mattmre/evokore-mcp-public/pr-manager"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/pr-manager.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.00028 | $0.01024 |
| Opus 5 | $0.00014 | $0.00512 |
| Sonnet 5 | $0.00006 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
pr-manager 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 7d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Manager
This skill manages outstanding PRs, ensuring code quality, feature completeness, and smart merging without losing context or code.
Core Workflows
1. PR Review and Merge Preparation
- We have a large amount of outstanding and open PRs.
- Use agentic orchestration to complete implementation of these items to prevent context rot.
- Provide agents with instructions and plans as needed, then dispose of the agent and use a fresh one.
- Before Implementation: Research and plan/architect all features. Coordinate analysis of current research and docs within the repo. If new research is done, save it to the
docsfolder. - Review Each PR: Check for comments, test/lint, and prepare for merge. Address and fix comments as needed. Update the PR once complete.
- Merge Smartly: Analyze as you go, test final before the final merge to main. Do not lose any coding we have; be as safe as possible.
- Tracking: Keep track of the session log and agents' work so we can track and monitor. Post a PR update for each so we can review.
2. Verification of Phase Features and Wiring
- Examine the feature requirements for each OPEN PR AND CLOSED PR.
- Verify the features were implemented or appear to be fully wired and flushed out.
- Prevent inline failures not explicitly exposed by the agents or models that would cause extensive re-writes.
- Produce a report of findings based on severity. Use multiple agents and orchestrate as needed to expedite.
3. Verification of Technical Deferment
- Do a sweep using multiple agents on all closed PRs AND open PRs for:
- Technical deferment
- Technical debt
- Features that were not implemented
- Any other issues noted in PR comments
- Ensure each PR is reviewed by Gemini if it hasn't been.
- Add these findings to the ARCH-AEP findings so we can remediate and tackle them all at once.
Risk-Based Review Routing
Adapted from Agent33's risk trigger framework. When a PR touches certain areas, it must be routed to the appropriate specialist reviewer before merge.
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.
- 7d ago First seen · 82 lines · 28 tokens per session scan A 82a40995ac4e
pr-manager is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 1,024 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-03.
Other skills, from other repositories
eg-precommit-review
Run a Codex-native pre-commit independent-review loop on pending changes.
oo-bitbucket
Bitbucket (bitbucket.org). Use this skill for ANY Bitbucket request — reading, creating, updating, and deleting data. Whenever a task involves Bitbucket, use this skill instead of calling the API directly.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
reviewing-changes
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.
github-review-pr
Review GitHub pull requests with evidence-backed, multi-perspective analysis and false-positive filtering. Use when the user asks to review, inspect, or check a GitHub pull request by number or URL. Default to reporting findings locally; publish comments, submit reviews, or approve only when the user explicitly…