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 assumptionsgit 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/assumptions)<a href="https://agentmods.dev/skills/yg3-ai/quill/assumptions"><img src="https://agentmods.dev/badge/skills/yg3-ai/quill/assumptions/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/yg3-ai/quill/assumptions"><img src="https://agentmods.dev/badge/skills/yg3-ai/quill/assumptions.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.00040 | $0.00842 |
| Opus 5 | $0.00020 | $0.00421 |
| Sonnet 5 | $0.00008 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
assumptions 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 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.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The developer just typed /quill:assumptions — they want to check the
technical choices you've been making silently. Their note: "$ARGUMENTS"
This isn't about defending what you've done. It's about making invisible choices visible so the developer can actually have an opinion. They are smart but don't necessarily know the vocabulary; your job is to surface your assumptions accurately, then let Quill translate them into questions they can answer.
Step 1 — Enumerate your assumptions
Look at what you've been working on (recent code, current plan, the direction of recent exchanges). List the technical assumptions you're currently making that the developer hasn't explicitly approved. Be honest and specific. Examples of what counts:
- Hosting / scale: single instance vs distributed, expected concurrent users, geographic distribution
- Data persistence: in-memory vs disk vs database, schema flexibility, backup posture
- Concurrency: sync vs async, locking strategy, ordering guarantees
- Failure handling: retry policy, fallback behavior, what happens on partial failure
- Security: trust boundaries, auth approach, secret handling, input validation
- Performance: caching, indexing, query patterns, payload size
- Data freshness: eventual vs strong consistency, polling vs push
- Future-proofing: extensibility, API stability, migration story
- Observability: logging, error reporting, what's monitored
Don't list theoretical assumptions. List the ones actually baked into what you're currently building or planning. Be concrete: "I'm assuming a single-process server with in-memory state" — not "I might assume something about hosting."
Length limit: keep your enumeration under 600 characters. The bridge caps inputs at 1000 chars and will truncate longer messages. Pick the load-bearing assumptions; skip the obvious ones.
Step 2 — Send to Quill for translation
Use this command, substituting your enumeration from Step 1 for <YOUR ASSUMPTIONS>:
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 · 85 lines · 40 tokens per session scan A 904e4a82eb99
assumptions is a skill published in the GitHub repository YG3-ai/quill (1 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 842 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.
output-standards
Use this skill when defining or enforcing output formatting standards for agent responses in WrongStack. Triggers: user says "next steps format", "output standard", "response format", "final message format", "standardize next steps".