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 akiotanaka847/qaio-desktop --skill log-a-decisiongit clone --depth 1 https://github.com/akiotanaka847/qaio-desktopWrote 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/akiotanaka847/qaio-desktop/log-a-decision)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/log-a-decision"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/log-a-decision/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/akiotanaka847/qaio-desktop/log-a-decision"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/log-a-decision.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.00058 | $0.01412 |
| Opus 5 | $0.00029 | $0.00706 |
| Sonnet 5 | $0.00012 | $0.00282 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
log-a-decision 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 7d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log A Decision
When to use
- User says "we decided", "log the decision on", "capture that call", "ADR this".
- Pasted/connected meeting notes contain clear decision pattern.
- User asks review open decision backlog - skill also marks
pendingrowsdecidedwhen user declares them.
Connections I need
I run external work through Composio. Before this skill runs I check the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.
- Meeting recorder (Fireflies, Gong) - Optional. Lets me pull a transcript when you say "log the call we just had." If not connected I work from what you paste.
- Docs / notes (Notion, Google Docs) - Optional. If you have a decision log or RACI doc elsewhere I read it before drafting.
This skill works without any connection. I never block here - worst case you describe the decision and I capture it.
Information I need
I read your operations context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.
- The decision itself - Required. Why I need it: I'm capturing one specific call, not generating one. If missing I ask: "What did you decide, and what was on the table before you picked?"
- Stakeholders and decider - Required. Why I need it: drives whether the row lands as pending or decided. If missing I ask: "Who decided this - you, a co-founder, the team - and is it final or still open?"
- Decision rights / RACI - Optional. Why I need it: lets me default the right status without asking each time. If you don't have it I keep going with TBD and ask once: "Who owns calls like pricing, hiring, or product strategy? A sentence is fine."
- Active priorities - Required. Why I need it: I tag whether the decision is load-bearing for what you're pushing on. If missing I ask: "What are the 2 to 3 things the company is pushing on this quarter?"
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.
- 7d ago First seen · 106 lines · 58 tokens per session scan A acc52226c108
log-a-decision is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 58 tokens to every session and 1,412 once invoked, about $0.0003 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-05.
Other skills, from other repositories
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
env-setup-assistant
Expert guide for setting up development environments including IDE configuration, tooling, dependencies, and developer onboarding. Use when bootstrapping new projects or standardizing team environments.
meeting-processor
Process meeting transcripts and Notion meeting notes into structured organizational records, action items, and memory updates.
mailroom-acknowledgement-sweep
Route unrouted mail and chase what nobody acknowledged.
asset-inventory-reconciliation
Reconcile recorded against observed assets.
committed-schedule-coordination
Keep committed schedule and reality in step.