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 decidegit 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/decide)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/decide"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/decide/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/decide"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/decide.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.00013 | $0.00502 |
| Opus 5.5 | $0.00005 | $0.00201 |
| Sonnet 5.5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
decide 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.
What it actually says
Decision Framework
Run any decision through the evaluation framework from system/04_decision_frameworks.md. Produces a structured recommendation.
Usage
/decide [decision or opportunity to evaluate]
Process
- Parse the decision — What's being decided? What are the options?
- Run relevant lenses — Not all 12 apply to every decision. Select the 4-6 most relevant:
- Leverage — disproportionate output?
- Alignment — advances an active priority?
- Reversibility — can it be undone?
- Time Sensitivity — does waiting cost anything?
- Revenue Impact — creates/protects/accelerates revenue?
- Asymmetry — large upside, bounded downside?
- Dependency — unblocks other work?
- Cost — money, time, attention?
- Compounding — gets better over time?
- Simplicity — simpler path available?
- Confidence — how certain are the inputs?
- Opportunity Cost — what are we NOT doing?
- Check against principal's decision framework —
system/14_decision_framework.md- Does it pass the pattern filter?
- Where does it sit in the priority stack?
- Does it pass the asymmetry test?
- Check authority level —
system/12_authority_matrix.md- Is this Level 1 (just do it), Level 2 (recommend), or Level 3 (human only)?
Output Format
DECISION: [What we're deciding]
OPTIONS: [A vs B vs C]
RECOMMENDATION: [What to do and why]
KEY LENSES: [3-4 lenses that drove the recommendation]
TRADE-OFF: [What we're giving up]
CONFIDENCE: [High / Medium / Low — and why]
AUTHORITY: [Level 1/2/3 — can the AIgent act or needs approval]
NEXT ACTION: [Specific immediate step]
Rules
- Be direct. Recommend, don't waffle.
- If confidence is low, structure it as an experiment, not a commitment.
- If it's Level 3, present the analysis but explicitly say "this is your call."
- Always name the trade-off. Every yes is a no to something else.
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 First seen · 57 lines · 13 tokens per session scan A f96dcac7317a
decide is a skill published in the GitHub repository wrg32786/aigent-os (24 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 502 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML…
insights
Use when the user types /weekly or /monthly, asks for a weekly or monthly journal review or retrospective, asks 'how was my week' or 'how was my month', or wants trends, anomalies, or patterns across recent journal entries. Also fires when regenerating an insight report for a past week or month. NOT for writing…
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
sunday-review
Use when the user asks for the weekly meta-review or Sunday wrap-up of their week and vault: says /sunday, /sunday-review, 'let's do the weekly review,' 'Sunday review,' 'review my week,' 'weekly retro,' 'week in review,' 'end-of-week review,' or wants journals, patterns, vault health, and stale decisions reviewed…
coach
Use when the user says /coach (today, week, month, profile, log), asks what to do today for training, asks for a workout, weekly training plan, or longevity plan, wants to log a finished workout or check lift progression (PR, plateau, deload), or a scheduled morning task fires to drop today's workout into the…