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 YG3-ai/quill --skill perspectivegit clone --depth 1 https://github.com/YG3-ai/quillWrote 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/yg3-ai/quill/perspective)<a href="https://agentmods.dev/skills/yg3-ai/quill/perspective"><img src="https://agentmods.dev/badge/skills/yg3-ai/quill/perspective.svg" alt="Measured on agentmods" 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.00041 | $0.00657 |
| Opus 5 | $0.00020 | $0.00329 |
| Sonnet 5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
perspective scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
import json, urllib.request, sys How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The developer just typed /quill:perspective — they're not stuck or
frustrated, they're exploring. They want to layer in another vantage point
alongside yours. Their note: "$ARGUMENTS"
This is additive, not corrective. Don't try to find what's wrong. Bring in something that opens up the possibility space.
Step 1 — Frame your current thinking
Look back at the last 6-10 exchanges in this session. In 2-3 sentences, describe:
- What the developer is exploring or building
- Your current angle on it (what you're focused on, what you've been proposing, what you find interesting about the problem)
- Where the thinking might benefit from another vantage point
Length limit: keep your framing under 600 characters total. The bridge caps inputs at 1000 chars and will truncate longer messages.
Step 2 — Ask Quill for the additional perspective
Use this command, substituting your framing from Step 1 for <YOUR FRAMING>:
python3 -c "
import json, urllib.request, sys
msg = sys.argv[1]
payload = json.dumps({'message': msg}).encode()
req = urllib.request.Request('http://127.0.0.1:9000/perspective', data=payload, headers={'Content-Type': 'application/json'})
try:
with urllib.request.urlopen(req, timeout=180) as r:
data = json.loads(r.read())
if data.get('welcome'):
print('=== WELCOME ===')
print(data['welcome'])
print('=== END WELCOME ===')
print()
print(data['reply'])
except Exception as e:
print(f'BRIDGE UNAVAILABLE: {e}')
" "<YOUR FRAMING>"
If you see BRIDGE UNAVAILABLE, the local advisor server isn't running.
Tell the developer to check the plugin's status (it should auto-start
when the plugin is enabled — see the plugin README for the recovery
command) and stop here.
First-install note: if the output contains === WELCOME === /
=== END WELCOME === markers, this is the developer's very first Quill
invocation. Show the welcome text (between the markers) verbatim as a
brief preface in Step 3, before the three-paragraph dialogue. After this
session it will never appear again — don't paraphrase or skip it.
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.
- 7d ago First seen · 73 lines · 41 tokens per session scan A 85e7f9dd9026
perspective is a skill published in the GitHub repository YG3-ai/quill (1 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 657 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
codex-delegate
Delegates implementation-heavy or repetitive coding work (batch edits, boilerplate, multi-file refactors with clear patterns, test scaffolding) from Claude to OpenAI Codex CLI. Use when token cost outweighs judgment cost. Trigger phrases include "delegate to codex", "let codex do this", "batch refactor across files"…
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…