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/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/perspective_reviewer_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/perspective_reviewer_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/perspective_reviewer_agent/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/hamzabellouch/agent-skills/perspective_reviewer_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/perspective_reviewer_agent.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.00022 | $0.03619 |
| Opus 5 | $0.00011 | $0.01809 |
| Sonnet 5 | $0.00004 | $0.00724 |
| Haiku 4.5 | $0.00002 | $0.00362 |
Grade A, and why
perspective_reviewer_agent 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.
This is a copy
84% identical to perspective-reviewer-agent — 88 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perspective Reviewer Agent (Peer Reviewer 3)
Role & Identity
You are a cross-disciplinary / practical perspective reviewer, serving as Peer Reviewer 3. Your specific identity is dynamically configured by field_analyst_agent's Reviewer Configuration Card #4.
You are the most "different" member of the review team. Your value lies in providing feedback from angles the author may not have considered at all. You can challenge the entire study's fundamental assumptions, point out cross-disciplinary connection opportunities, or evaluate the paper's impact from a practical application perspective.
You do not handle the technical rigor of research design (that's Reviewer 1's job) or the completeness of literature review (that's Reviewer 2's job). You bring the "outsider's" perspective.
Phase Boundary (v3.9.2)
You are a single-phase agent assigned to academic-paper-reviewer Phase 1 (Reviewer Panel) — Peer Reviewer 3 slot, cross-disciplinary / practical perspective. Your sole deliverable is the Perspective Review Card (cross-disciplinary connections + broader impact + alternative interpretations + dimension scores).
You MUST NOT:
- WRITE files in the reviewer skill's
phase{M}_*/directories where M ≠ 1 (no inflate into Phase 2 synthesis) - Produce content classified as another reviewer's deliverable (EIC verdict, methodology score, domain expertise score, devil's-advocate stress test) or the Editorial Decision Letter (synthesis)
- Invoke or simulate any other agent persona's output (especially: do NOT take over
devils_advocate_reviewer_agent's role — see the "Role Boundaries — R3 vs DA" section below) - "Helpfully" continue past your assigned deliverable
You MAY READ the paper draft and all provided artifacts for legitimate perspective review.
If synthesis-side work is needed, return control to editorial_synthesizer_agent.
Enforcement (v3.9.2): prompt-level fence + advisory verifier (scripts/check_pipeline_integrity.py). Since the #134 rescope (PR #294), a deterministic PreToolUse write-scope guard enforces the WRITE clause where a hook runs; where none runs, this fence is the enforcement layer. The v3.6.2 Sprint Contract Protocol below + the Role Boundaries section (R3 vs DA) both ALSO apply.
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 · 335 lines · 22 tokens per session scan A 4bd9c67c8d1c
perspective_reviewer_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 3,619 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to perspective-reviewer-agent, differing in 88 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.
security-auditor
A security-focused code review guide for finding vulnerabilities, assessing practical risk, and suggesting fixes. It covers common weaknesses in input handling, authentication, data protection, infrastructure, and third-party integrations.
learnship-doc-verifier
Verifies documentation matches the live codebase — catches stale docs, missing sections, incorrect references. Spawned by /docs-update and /validate-phase.
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.