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 agentmods add skills/cofin/flow/perspectivesnpx skills add cofin/flow --skill perspectivesgit clone --depth 1 https://github.com/cofin/flowWhat 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 | $0.00032 | $0.00293 |
| Opus 5 | $0.00016 | $0.00147 |
| Sonnet 5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
perspectives 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 2d 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.
What it actually says
Perspectives
Apply explicit advocate, critic, and neutral views, then synthesize them without artificial balance.
Workflow
- Load the synthesis method and stance definitions below.
- State the core claim or decision and the evidence available to every view.
- Apply each stance, then use the synthesis method to reach an actionable conclusion.
Guardrails
Do not manufacture 50/50 balance, conceal assumptions, or let a stance override security, privacy, ethical, or verified technical constraints.
Output
Return the core decision, distinct advocate/critic/neutral findings, decisive assumptions and risks, and a synthesized recommendation with next actions.
Validation
Confirm all three views are distinct, evidence-based, and accurately weighted in the synthesis.
Example
For a service-boundary proposal, contrast scaling benefits, operational costs, and evidence-based adoption conditions before recommending a direction.
References
- Critical-thinking and synthesis method — verification and multi-view synthesis.
- Stance definitions — advocate, critic, and neutral views.
What ships with it
3 files 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.
- 2d ago First seen · 58 lines · 32 tokens per session scan A 143e651a5bf1
perspectives is a skill published in the GitHub repository cofin/flow (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 32 tokens to every session and 293 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
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
write-documentation
Use when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read. Not for code comments, commit messages, or agent-to-agent communication.
document-release
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.