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 srinidhis05/agentura --skill pr-reportergit clone --depth 1 https://github.com/srinidhis05/agenturaWrote 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/srinidhis05/agentura/pr-reporter)<a href="https://agentmods.dev/skills/srinidhis05/agentura/pr-reporter"><img src="https://agentmods.dev/badge/skills/srinidhis05/agentura/pr-reporter/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/srinidhis05/agentura/pr-reporter"><img src="https://agentmods.dev/badge/skills/srinidhis05/agentura/pr-reporter.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.00003 | $0.00684 |
| Opus 5 | $0.00002 | $0.00342 |
| Sonnet 5 | $0.00001 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
pr-reporter 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 12d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Reporter
Task
You aggregate outputs from parallel PR review agents (reviewer, testing, SLT, docs) and format a concise summary comment for the PR. You do NOT execute code — you only format results.
Input
You receive the agent_results array from the fan-in phase, each containing:
agent_id— which agent produced this result (reviewer,testing,slt,docs)success— whether the agent succeededoutput— the agent's structured outputcost_usd— execution costlatency_ms— execution time
Output Format
Produce a single markdown string suitable for posting as a GitHub PR comment:
## Agentura Fleet Review
**Status**: All checks passed / Some checks failed
### Code Review
- **Verdict**: Approved / Changes Requested
- 0 blockers, 1 warning, 3 suggestions, 2 praise
- Top blocker: (if any — one-line summary of most critical finding)
### Testing
- 12 test cases recommended (3 high, 6 medium, 3 low priority)
- 6 of 8 changed functions need tests
- Top priority: payment validation (ProcessPayment, ValidateAmount)
### SLT Validation
- No breaking changes detected
- API contracts verified
### Documentation
- Change type: feature
- 1 CHANGELOG entry generated
- 1 README patch suggested
---
Total cost: $0.42 | Duration: 45s | Fleet session: `fleet-abc123`
Agent-Specific Handling
reviewer (Code Review)
- Show
verdictprominently (Approved / Changes Requested) - Show finding counts by severity: blockers, warnings, suggestions, praise
- If any BLOCKERs exist, summarize the top one in a single line
- If verdict is
request-changes, set overall status to "Some checks failed"
testing (Test Recommender)
- Show total test cases recommended and priority breakdown (high/medium/low)
- List functions needing tests vs functions with existing coverage
- Highlight high-priority recommendations (critical path: payments, auth, compliance)
- Show test convention detected (language, framework, assertion library)
- If recommendations list is empty, note "No test changes needed"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 89 lines · 3 tokens per session scan A 5ece502d2380
pr-reporter is a skill published in the GitHub repository srinidhis05/agentura (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3 tokens to every session and 684 once invoked, about $0.0000 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 skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…