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 synaptiai/synapti-marketplace --skill making-decisionsgit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/making-decisions)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/making-decisions"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/making-decisions/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/synaptiai/synapti-marketplace/making-decisions"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/making-decisions.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.00025 | $0.01475 |
| Opus 5 | $0.00013 | $0.00737 |
| Sonnet 5 | $0.00005 | $0.00295 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
making-decisions 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 10d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision Ledger
This skill guides the creation of explicit decisions with full trade-off documentation.
Prerequisites
- Synthesis complete (
/ledger-synthesize) 03-synthesis/CROSS-SYNTHESIS.mdexists with decision candidates- Per-pillar syntheses in
03-synthesis/SYN-*.md
Workflow
Use TodoWrite to track these mandatory steps:
Step 1: Load Decision Candidates
Read 03-synthesis/CROSS-SYNTHESIS.md to extract:
- Decision topics needing resolution
- Supporting evidence from each pillar
- Identified options
Step 2: Gather Evidence per Decision
For each decision candidate:
- Collect all relevant EV-* IDs
- Summarize what evidence supports each option
- Note confidence levels
decision_candidate:
topic: target-segment-priority
options:
- name: SMB-first
evidence:
- EV-users-smb-pain-points (0.80)
- EV-economics-smb-unit-economics (0.75)
- name: Enterprise-first
evidence:
- EV-market-enterprise-tam (0.85)
- EV-competitors-enterprise-gap (0.70)
Step 3: Present Trade-offs
For each decision, present:
- Options with evidence support
- What you win with each option
- What you lose with each option
- Risks created by each option
Use AskUserQuestion to get user's decision.
Step 4: Create Decision Entry
Write entry to 04-decisions/DECISIONS.yaml using schema from references/decision-ledger-schema.md.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 232 lines · 25 tokens per session scan A f87999e537a8
making-decisions is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 1,475 once invoked, about $0.0001 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
create-or-update-concepts
Scan and analyze the project codebase to create or update concept files in agents-context/concepts/ (organized by domains/, source/, shared/) and update the README index and Load-When Cheatsheet.
step2-scope-tasks
Break a specification into ordered task groups with explicit context-awareness directives.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
step4-archive-spec
Archive a completed spec — moves it to specs-archived and blocks agent access.
plan-product
Define product mission, vision, target users, and technology stack.