Borrowing it
Nothing to install: this file belongs to katopz/katgpt-rs. 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/katopz/katgpt-rs/develop/.agents/skills/proposal/SKILL.mdgit clone --depth 1 https://github.com/katopz/katgpt-rsWrote 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/katopz/katgpt-rs/proposal)<a href="https://agentmods.dev/skills/katopz/katgpt-rs/proposal"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/proposal/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/katopz/katgpt-rs/proposal"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/proposal.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.00114 | $0.05071 |
| Opus 5.5 | $0.00046 | $0.02028 |
| Sonnet 5.5 | $0.00023 | $0.01014 |
| Haiku 4.5 | $0.00011 | $0.00507 |
Grade A, and why
proposal 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 1mo 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proposal — Reasoned architectural argument with codebase grounding + prior art
A proposal is the layer between research (paper distillation) and plan
(task execution). It argues for an architectural change, a new primitive, or a
design decision — grounded in (a) what the codebase already ships, (b) what
sibling repos have already proposed, and (c) what the literature says. It is
not a paper summary, not a task list, and not an audit.
The deliverable is a .proposals/NNN_*.md file in the repo that owns the
affected surface, written in the established proposal format (see §Output
format). It MUST ship with honest caveats and a fusion lineage — these are
non-negotiable per the canonical proposals in katgpt-rs/.proposals/.
When to use
- The user asks "should we do X?" / "what if we Y?" / "propose a design for Z".
- A design question spans multiple primitives, repos, or feature flags and needs a reasoned argument before any plan is opened.
- A new feature wants GOAT-gate discipline but the design is still open — the proposal settles the design, the plan executes it.
- A cross-repo change touches the sync boundary, freeze/thaw, or raw↔latent bridge and needs the boundary rule reasoned through explicitly.
DO NOT use for
- Paper distillation → use the
researchskill. Proposal may cite a paper as prior art but does not distill it. - Task execution → write a
.plans/NNN_*.md. Proposals sketch a phased rollout; plans own the- [ ]task list. - POC / refactor / optimization tracking → file
.issues/NNN_*.mdper the global rule ("Create issue at .issues for poc, proof, optimization or refactor task, do not create plan"). - Cross-repo GOAT cherry-pick audit → use the
goat-auditskill. - Bug fixes with no architectural angle.
Repos in scope (the product/distillation set — 7)
Same layout as the research and goat-audit skills. Canonical home for this
list: katgpt-rs/AGENTS.md §"Repo count" (and Research 003) — it is copied
here for reading convenience, so when the two disagree, AGENTS.md wins. This
copy said "7-repo stack" and omitted riir-dapps from 2026-08-20 until
2026-09-01, then read "8" — correct for the one day before riir-armageddon's
retirement (2026-09-02) took the set back to 7, and stale from that day until
2026-09-11. That is what a duplicated count does:
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.
- 1mo ago Changed e94e41665def
- 1mo ago Changed · +2 lines ed991d4c59f2
- 1mo ago Changed · +1 lines f3c2fd978f25
- 1mo ago Changed · +20 lines 1f4a2efde9c2
- 2mo ago First seen · 380 lines · 114 tokens per session scan A c5b9e76bedc4
proposal is a skill published in the GitHub repository katopz/katgpt-rs (140 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 5,071 once invoked, about $0.0005 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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…