Borrowing it
Nothing to install: this file belongs to minorcell/aquaregia. 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/minorcell/aquaregia/main/.agents/skills/writing-proposals/SKILL.mdgit clone --depth 1 https://github.com/minorcell/aquaregiaWrote 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/minorcell/aquaregia/writing-proposals)<a href="https://agentmods.dev/skills/minorcell/aquaregia/writing-proposals"><img src="https://agentmods.dev/badge/skills/minorcell/aquaregia/writing-proposals/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/minorcell/aquaregia/writing-proposals"><img src="https://agentmods.dev/badge/skills/minorcell/aquaregia/writing-proposals.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.00060 | $0.01861 |
| Opus 5.5 | $0.00024 | $0.00744 |
| Sonnet 5.5 | $0.00012 | $0.00372 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade A, and why
writing-proposals 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 2mo 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.
Writing Proposals
Overview
Write proposals as small, reviewable design increments. The goal is not to describe a whole system at once; the goal is to isolate the next necessary design decision, express it simply, remove avoidable complexity, define boundaries, and ground the change in real user stories.
A good proposal makes a reviewer able to decide, an implementer able to build, and a maintainer able to verify. Format is secondary to this thinking model.
Core Thinking Model
1. Design Progressively
One proposal should settle one clear increment. Do not try to explain every related subsystem, future extension, or complete architecture in a single proposal.
Use follow-up proposals for adjacent decisions. Prefer a narrow proposal that can be accepted, implemented, and tested over a broad proposal that tries to solve the whole future.
2. Prefer Simple, Direct Expression
Choose the expression a reader can understand immediately. If one realistic example explains the design, lead with the example before abstract definitions. If one rule can explain the behavior, do not introduce multiple mechanisms.
The design should be short, teachable, implementable, and easy to remember.
3. Do Subtractive Design
The proposal should reduce redundancy or accidental complexity. Look for opportunities to remove:
- boilerplate code
- manual steps
- repeated configuration
- exposed intermediate mechanisms
- special cases users must remember
- duplicated concepts across similar workflows
Do not add features for completeness. Add the smallest design that lets the system absorb repeated work or remove unnecessary user burden.
4. Define Boundaries Carefully
Make the limits explicit:
- what this proposal solves
- what it does not solve
- which cases are valid
- which cases are errors
- whether existing behavior changes
- what workaround exists today
- where this design meets existing mechanisms
Clear boundaries prevent a proposal from expanding into a large system design.
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.
- 2mo ago First seen · 253 lines · 60 tokens per session scan A 29e7ca1ceb21
writing-proposals is a skill published in the GitHub repository minorcell/aquaregia (10 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,861 once invoked, about $0.0002 per session on Opus 5.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.
writing-proposals compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| writing-proposalsminorcell/aquaregia | Skill | 10 | 2mo ago | MIT | A | 60 | Claude Code, Codex |
| html-artifactslangchain-ai/open-swe | Skill | 11k | yesterday | MIT | A | 52 | Claude Code, Codex |
| web-appslangchain-ai/open-swe | Skill | 11k | yesterday | MIT | A | 43 | Claude Code, Codex |
| baby-sitlangchain-ai/open-swe | Skill | 11k | yesterday | MIT | A | 30 | Claude Code, Codex |
| workspaceslangchain-ai/open-swe | Skill | 11k | yesterday | MIT | A | 88 | Claude Code, Codex |
| linear-ticketslangchain-ai/open-swe | Skill | 11k | yesterday | MIT | A | 44 | Claude Code, Codex |
| connectlangchain-ai/open-swe | Skill | 11k | yesterday | MIT | A | 20 | Claude Code |