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 bjorn-ingmanson/thefroject-plugins --skill decision-trackergit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/decision-tracker)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/decision-tracker"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/decision-tracker.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.00027 | $0.00649 |
| Opus 5 | $0.00014 | $0.00324 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
decision-tracker 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision Tracker
Writes
outputs/decisions.md
Step 1: Load Existing Log
Read outputs/decisions.md if it exists. If it does not exist, create it with the header structure below.
Step 2: Determine Action
Ask: Are you recording a new decision, or reviewing existing ones?
Ask one question at a time. If the user gives a vague answer, push back and ask for specifics before proceeding.
Recording a New Decision
Gather:
- What was decided? — One clear sentence
- Context — What prompted this decision? What alternatives were considered?
- Rationale — Why this option over the alternatives?
- Who decided? — Person or group
- Scope — What does this affect? (architecture, process, hiring, product, messaging)
Classify the new decision:
- NEW — Just made, not yet tested
Check existing decisions for conflicts. If the new decision contradicts an existing one, flag it and ask the user to resolve.
Reviewing Existing Decisions
Read the log and update statuses:
- STABLE — Confirmed multiple times, still valid
- VOLATILE — Changed recently or under reconsideration
- CONFLICTING — Contradicts another decision in the log
- NEW — Recently added, not yet validated
For each decision, ask: Is this still true? Has anything changed?
Output Format
Maintain outputs/decisions.md with this structure:
Decision Log
Last updated: [date]
Active Decisions
| # | Decision | Status | Date | Decided By | Scope |
|---|---|---|---|---|---|
| 1 | [decision] | STABLE | [date] | [who] | [scope] |
| 2 | [decision] | NEW | [date] | [who] | [scope] |
Decision Details
Decision #1: [short title]
- Status: STABLE
- Date: [date]
- Decided by: [who]
- Context: [what prompted it]
- Rationale: [why this option]
- Alternatives considered: [what else was on the table]
- Affects: [what this decision impacts]
Archived Decisions
Decisions that were reversed or superseded. Keep for history.
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 · 84 lines · 27 tokens per session scan A 90d1cfe6f055
decision-tracker is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 649 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…