Borrowing it
Nothing to install: this file belongs to safety-quotient-lab/psychology-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/safety-quotient-lab/psychology-agent/main/.claude/skills/scan-peer/SKILL.mdgit clone --depth 1 https://github.com/safety-quotient-lab/psychology-agentWrote 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/safety-quotient-lab/psychology-agent/scan-peer)<a href="https://agentmods.dev/skills/safety-quotient-lab/psychology-agent/scan-peer"><img src="https://agentmods.dev/badge/skills/safety-quotient-lab/psychology-agent/scan-peer/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/safety-quotient-lab/psychology-agent/scan-peer"><img src="https://agentmods.dev/badge/skills/safety-quotient-lab/psychology-agent/scan-peer.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.00032 | $0.02252 |
| Opus 5 | $0.00016 | $0.01126 |
| Sonnet 5 | $0.00006 | $0.00450 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade A, and why
scan-peer 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 11d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scan-peer — Peer Content Quality Scan
Scan a peer agent's repository content for quality issues. Produce structured findings in interagent/v1 format and deliver to the appropriate transport session.
Designed for autonomous operation within the interagent feedback loop.
Arguments
Parse $ARGUMENTS for:
| Argument | Default | Meaning |
|---|---|---|
<peer-name> |
required | Peer to scan: unratified |
--since <commit> |
last 5 commits | Only scan files changed since this commit |
--session <id> |
content-quality-loop |
Transport session to write findings to |
Peer Registry
| Peer | Local clone | Content paths | Glossary |
|---|---|---|---|
| unratified | ~/Projects/unratified |
src/pages/, src/content/, blog/src/content/ |
src/data/glossary.ts (49 terms) |
Protocol
Phase 1: Identify Changed Content
cd ~/Projects/unratified
git fetch origin
# Use --since commit or default to last 5 commits
git diff --name-only HEAD~5..HEAD -- src/pages/ src/content/ blog/src/content/
Filter to content files only: .mdx, .md, .astro (pages with prose), .ts (data files with user-facing text).
If no content files changed, write a "no-findings" message and stop.
Phase 1b: Diff Verification (false-positive guard)
Before passing changed files to Phase 2, filter out non-changes:
- Skip empty-file diffs — if both sides of the diff exist but contain identical content (rename-only, mode change), exclude the file
- Ignore whitespace-only diffs — run
git diff --ignore-all-spaceon each file. If the whitespace-insensitive diff produces no output, exclude the file. Exception: YAML frontmatter (between---delimiters) and Markdown table rows (lines matching^\|) treat whitespace as significant — keep these files - Verify both sides exist — if
git diffreports a file as "added" but the file existed in the prior commit (rename detection), verify the content actually changed. A diff against a non-existent file reports the entire file as new content, which inflates findings - Log filtered files — record
files_filteredcount and reasons in the transport payloadscan_rangeblock for audit trail
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.
- 11d ago First seen · 253 lines · 32 tokens per session scan A 4b4a970a2a2f
scan-peer is a skill published in the GitHub repository safety-quotient-lab/psychology-agent (20 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 2,252 once invoked, about $0.0002 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-30.
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.
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…
go-concurrency-safety
L1 supplement - audits Go-specific concurrency hazards in node client code: map iteration non-determinism, goroutine leaks, mutex ordering, panic boundaries, context cancellation.