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 HirogaKatageri/hirokata --skill multi-perspective-scangit clone --depth 1 https://github.com/HirogaKatageri/hirokataWrote 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/hirogakatageri/hirokata/multi-perspective-scan)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/multi-perspective-scan"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/multi-perspective-scan/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/hirogakatageri/hirokata/multi-perspective-scan"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/multi-perspective-scan.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.00141 | $0.01026 |
| Opus 5 | $0.00071 | $0.00513 |
| Sonnet 5 | $0.00028 | $0.00205 |
| Haiku 4.5 | $0.00014 | $0.00103 |
Grade A, and why
multi-perspective-scan 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Perspective Scan — The Five Lenses, Standalone
When you ask one question, you get the majority view — one framing, the surface. The
breakthrough behind Stanford's STORM is simple: ask the same topic from five independent
expert lenses and you catch the blind spots a single pass never sees. This skill runs just
that fan-out — fast, when you don't need the full contradiction map / synthesis / peer-review
pipeline (for that, use storm-research).
The five lenses, and what each uniquely catches:
| Lens | Sees what others miss |
|---|---|
| Practitioner | The theory–practice gap; what actually works in the field |
| Skeptic | Overclaims, hidden flaws, the buried failure cases |
| Economist | Who profits, who pays, the misaligned incentives |
| Historian | The pattern that repeated before; where we are in the cycle |
| Academic | What the evidence actually shows, including conflicting findings |
Workflow
Step 0 — Scope
- Get the topic. If vague or sprawling, ask one sharpening question. A tight topic yields sharper perspectives.
- Derive a slug and set the workspace
.storm/{slug}/. Create it:mkdir -p .storm/{slug}. - Tune the panel if a swap clearly helps (e.g. add a Clinician / Regulator / End User via a Task call using the same persona output contract). Default to the standard five.
Step 1 — Fan Out (parallel)
Launch all five persona agents in a single message with five Task calls. Each gets the topic, the workspace path, and its output file. Per-agent prompt:
"Topic: {topic}. Workspace:
.storm/{slug}/. Write your analysis to.storm/{slug}/{persona}.mdper your output contract. Gather real evidence with WebSearch/WebFetch and cite it."
Targets: practitioner.md, skeptic.md, economist.md, historian.md, academic.md.
Each agent writes its file and returns a one-line confirmation. If one fails, note it and
continue with the rest.
Step 2 — Present the Five Views
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 · 95 lines · 141 tokens per session scan A 1a395a1a1f3c
multi-perspective-scan is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed today), licensed MIT. It adds 141 tokens to every session and 1,026 once invoked, about $0.0007 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
unslop
Humanize LLM output so it reads like a careful human wrote it. Subtracts AI-isms (sycophancy, tricolons, em-dash overuse, "delve"/"tapestry"/"testament", hedging stacks, tidy five-paragraph shapes), engineers burstiness and calibrated uncertainty, and preserves technical accuracy. Supports intensity levels: subtle…
unslop-file
Humanize natural-language memory files (CLAUDE.md, todos, preferences, docs) by removing AI-isms and adding burstiness while preserving every code block, URL, path, command, and heading exactly. Two modes: --deterministic (fast, regex-based, no API) and LLM (default, calls Claude for rewrite). Humanized version…
unslop-commit
Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why"…
unslop-help
Quick-reference card for unslop modes, sub-skills, and slash commands. One-shot display, not a persistent mode. Trigger: /unslop-help, "unslop help", "what unslop commands", "how do I use unslop".
simulator-charts
Simulator.Company chart and dashboard specialist. Use when the user wants to create, configure, or query charts (line, bar, area), dashboards, or financial time-series visualisations on a graph layer. Trigger on any of these intents: — Creating: "create chart", "add chart", "create dashboard", "add dashboard", "build…
simulator-init
Simulator.Company environment setup specialist. Use when the user wants to connect to Simulator.Company, set up credentials, authenticate, configure the workspace, or start working with Simulator for the first time. Activate when the user says "init", "setup", "connect to simulator", "login to simulator", "configure…