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/sananthanarayan/skilldrop/decision-lognpx skills add sananthanarayan/skilldrop --skill decision-loggit clone --depth 1 https://github.com/sananthanarayan/skilldropWrote 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/sananthanarayan/skilldrop/decision-log)<a href="https://agentmods.dev/skills/sananthanarayan/skilldrop/decision-log"><img src="https://agentmods.dev/badge/skills/sananthanarayan/skilldrop/decision-log.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.1 | $0.00084 | $0.00940 |
| Opus 5 | $0.00042 | $0.00470 |
| Sonnet 5 | $0.00017 | $0.00188 |
| Haiku 4.5 | $0.00008 | $0.00094 |
Grade A, and why
decision-log 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
decision-log
You help the user turn messy meeting notes or threads into a structured log of what was decided, who owns the follow-up, and what's still open.
How to respond
-
Ingest the source. The user will paste notes, give a file path, or share a transcript. If the source is huge (e.g., a 90-minute transcript), confirm scope: "Are you only interested in decisions, or also action items and open questions?"
-
Extract four categories:
- Decisions made. Things the group agreed on — even if informal. Look for phrases like "we'll go with…", "let's do…", "agreed", "fine by me", "ship it". Capture the decision in active voice, with a one-line why if it's in the source.
- Action items. Things someone agreed to do. Need an owner (a name), an action (a verb phrase), and ideally a due date. If the date is fuzzy ("by next week"), convert to an absolute date and flag it.
- Open questions. Things explicitly not resolved. Include who needs to answer if it's stated.
- Risks raised. Concerns that were aired but not resolved — useful for the next meeting's agenda.
-
Convert fuzzy dates to absolute dates. "Friday" →
YYYY-MM-DD. "End of week" →YYYY-MM-DD (EOW). "Next sprint" → ask the user when the next sprint ends if it's not in the source. Mark dates as(implied)when you've inferred them so the user can verify. -
Attribute every action item to a named person. "Someone should…" is not a tracked action — flag those as "unowned" so the user can assign in the meeting.
-
Output as four tables, in this order:
## Decisions | # | Decision | Why | Source | |---|---|---|---| ## Action items | # | Owner | Action | Due | Source | |---|---|---|---|---| ## Open questions | # | Question | Owner (to answer) | Source | |---|---|---|---| ## Risks raised (not yet acted on) | # | Risk | Raised by | Source | |---|---|---|---|The
Sourcecolumn quotes ~5–10 words from the original notes so the user can verify nothing was hallucinated.
What ships with it
3 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.
- 5d ago First seen · 68 lines · 84 tokens per session scan A 6cdf5c709cfa
decision-log is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 21d ago), licensed MIT. It adds 84 tokens to every session and 940 once invoked, about $0.0004 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
openlore-plan-refactor
Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
team-repair
Re-index OKF v0.2 index.md/log.md files, derive CDR.md, rebuild .skills.json and AGENTS.md in team-ai-directives, migrate v0.1→v0.2 frontmatter, scan for rule conflicts, and verify directive freshness. Use when indexes are inconsistent, orphans are detected, after bulk changes, or for periodic team AI directives…