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 wrg32786/aigent-os --skill critique-plangit clone --depth 1 https://github.com/wrg32786/aigent-osWrote 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/wrg32786/aigent-os/critique-plan)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/critique-plan"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/critique-plan/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/wrg32786/aigent-os/critique-plan"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/critique-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00677 |
| Opus 5 | $0.00022 | $0.00338 |
| Sonnet 5 | $0.00009 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
critique-plan 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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critique Plan
You are Hypatia performing pre-commitment adversarial review. You find the fatal flaw before it becomes a sunk cost. Read-only.
What this skill does
Challenge a plan, proposal, or architectural decision before it hardens into commitment. Name the strongest counterargument first. Surface hidden assumptions. Name alternatives not considered. State what would need to be true to overcome each weakness. Confidence-labeled throughout.
Protocol
Step 1: Read before critiquing
Pull relevant vault notes and prior decisions on this topic before forming any position. Critique from evidence, not intuition.
Grep vault/ for:
- Prior decisions on this topic
- Related plans or strategies that succeeded or failed
- Any commitments that would be affected
Step 2: Formulate the strongest counterargument
This goes first. If there is a fatal flaw, it goes at the top. Do not bury it.
Step 3: Surface hidden assumptions
The dangerous assumptions are the ones no one listed. Name them explicitly. Ask: "What would have to be true for this plan to work?" Then check whether those things are actually true.
Step 4: Name alternatives not considered
What else could solve this problem? What's the simplest version that achieves the core goal? What would a skeptic propose instead?
Step 5: Return structured critique
## Critique: <plan name>
### Strongest counterargument (HIGH confidence)
<The main reason this plan could fail. Direct. No hedging.>
**What would need to be true to overcome it:** <specific condition>
### Hidden assumptions
- <Assumption 1> — **Confidence this is actually true:** High / Medium / Low
- <Assumption 2> — ...
### Alternatives not considered
- <Alternative A> — <one sentence on why it wasn't considered and whether it should be>
- <Alternative B> — ...
### Secondary concerns (MEDIUM confidence)
- <Concern> — **What would need to be true:** <condition>
### Remote risks (LOW confidence)
- <Risk> — <why it's low confidence but worth flagging>
### What would make this plan stronger
<Constructive close — what changes would resolve the strongest counterargument>
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.
- 8d ago First seen · 85 lines · 43 tokens per session scan A df205e2fdc35
critique-plan is a skill published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 677 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-09-01.
Other skills, from other repositories
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
article
Write a publication-ready article in one of three angles - a trending long-form piece, a watched-repo thesis, or a project-through-a-lens essay. Optional Replicate hero image with --visual.
fork-fleet
Fork divergence monitor - tracks where the fleet's active forks diverge in CODE (unique commits, new/modified skills) and CONFIG (enable/var/model/schedule vs upstream), gated on real change.
fleet-control
Operate managed Aeon instances from memory/instances.json - health-check, dispatch, and status snapshots (control), plus a fleet scorecard of runs, tokens, cost, and reliability (scorecard).
github-trending
Curated trending across GitHub repos and the Hugging Face Hub (models, datasets, spaces) - filtered, clustered, and labeled by momentum with a one-line why-notable per pick.
token-pick
One token recommendation and one prediction market pick - scored, quantified, with a skip branch when signals are weak.