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 bostonaholic/rpikit --skill documenting-decisionsgit clone --depth 1 https://github.com/bostonaholic/rpikitWrote 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/bostonaholic/rpikit/documenting-decisions)<a href="https://agentmods.dev/skills/bostonaholic/rpikit/documenting-decisions"><img src="https://agentmods.dev/badge/skills/bostonaholic/rpikit/documenting-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/bostonaholic/rpikit/documenting-decisions"><img src="https://agentmods.dev/badge/skills/bostonaholic/rpikit/documenting-decisions.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.00047 | $0.01631 |
| Opus 5 | $0.00023 | $0.00816 |
| Sonnet 5 | $0.00009 | $0.00326 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
documenting-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 9d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documenting Decisions
Capture architectural decisions as Architecture Decision Records (ADRs).
Purpose
Design decisions made during brainstorming and planning need a standardized, discoverable format for long-term reference. ADRs record what was decided, why, and what alternatives were considered. This skill reads design documents and produces structured ADR files that provide historical context for future engineers.
When to Use
Use this skill when:
- A design decision has been made during brainstorming or planning
- An architectural choice needs to be recorded for posterity
- You want to document why an approach was chosen over alternatives
- A previous decision is being superseded or deprecated
Skip this skill when:
- The decision is trivial (formatting, naming conventions)
- No alternatives were considered
- The change is temporary or experimental
Process
1. Identify the Design Document
Parse $ARGUMENTS for a path to a design document.
Path validation: Before reading, verify the path is safe:
- Reject absolute paths (starting with
/or~) - Reject paths containing
..segments - Only accept relative paths within the project directory
- If invalid, inform the user and ask for a relative path under
docs/
If a valid path is provided:
- Read the design document
- Extract: problem statement, chosen approach, alternatives, trade-offs
If no path is provided:
- Search for recent design documents:
Glob pattern: docs/plans/*-design.md
- Present found documents and ask user to select one using AskUserQuestion
- If no design documents exist, ask user to describe the decision directly
2. Extract Decision Content
From the design document (or user input), identify:
- Title: A short, imperative description of the decision
- Context: The problem being solved and relevant background
- Decision: What was chosen and why
- Consequences: Positive and negative outcomes
- Alternatives: Other options considered and why they were rejected
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.
- 9d ago First seen · 253 lines · 47 tokens per session scan A 1ba38be9116d
documenting-decisions is a skill published in the GitHub repository bostonaholic/rpikit (20 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 1,631 once invoked, about $0.0002 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-30.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
api-docs
Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.
research
Run deep research on any topic using the Deep Research MCP server. Use this skill whenever the user wants to research a topic, gather information, find sources, or create a research document. Triggers on: 'research this', 'find out about', 'gather information on', 'I need to understand', 'deep dive into', or any…
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.
Workspace Data Analyst
Analyze CSV files in the workspace and summarize insights.
run_jinx
Execute a jinx by name (already loaded on the team) or by filesystem path (e.g. a freshly createdjinx that isn't yet registered), passing input values as a JSON object. Returns the jinx's output field or the full context dict. Use this to run a jinx you just wrote without exiting the session.