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/dixus/claudeframework/apply-proposalsnpx skills add dixus/claudeframework --skill apply-proposalsgit clone --depth 1 https://github.com/dixus/claudeframeworkWrote 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/dixus/claudeframework/apply-proposals)<a href="https://agentmods.dev/skills/dixus/claudeframework/apply-proposals"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/apply-proposals.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 | $0.00040 | $0.01505 |
| Opus 5 | $0.00020 | $0.00753 |
| Sonnet 5 | $0.00008 | $0.00301 |
| Haiku 4.5 | $0.00004 | $0.00151 |
Grade A, and why
apply-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 5d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply accepted proposals from .claude/reviews/learn-proposals.md to the target skill and rule files.
$ARGUMENTS is optional:
--all— apply all proposals with Statusaccepted--proposal <N>— apply only proposal number N (by order of appearance), regardless of Status- No arguments — interactive mode: present pending proposals for review, then apply accepted ones
Step 0 — Load proposals
- Read
.claude/reviews/learn-proposals.md. If the file doesn't exist, report "No proposals file found. Run/scoutor/learnfirst." and stop. - Parse each proposal block. A proposal starts with
### Skill:or### New skill:or### Rule:and contains:**What:**— one-line description**Why:**— motivation**Source:**or**Source tier:**— provenance**Status:**— pending / accepted / rejected / deferred**Diff:**— the proposed change (old → new)
- Build a numbered list of all proposals with their Status.
Step 1 — Select proposals to apply
If --all: select every proposal with Status accepted.
If --proposal <N>: select only that proposal. If its Status is not accepted, ask: "Proposal #N has status <status>. Apply anyway? (Y/N)" — proceed only if Y.
If no arguments (interactive mode):
- Print all proposals in a numbered table:
| # | Target | What | Status | Tier | | -- | ----------------- | ----------------------------- | -------- | ---- | | 1 | /2_review | Add disallowedTools | pending | T1 | | 2 | /3_fix | Add maxTurns: 15 | pending | T1 | - Ask: "Which proposals to apply? Enter numbers (e.g.
1,3,5),allfor all pending, orqto quit." - For each selected proposal, update its Status to
acceptedinlearn-proposals.mdbefore applying.
If no proposals are selected (or all are already accepted/rejected), report and stop.
Step 2 — Validate diffs before applying
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.
- 5d ago First seen · 132 lines · 40 tokens per session scan A 46934255fbce
apply-proposals is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,505 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…