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/hoavdc/codexkit/codexkit-decision-lognpx skills add hoavdc/CodexKit --skill codexkit-decision-loggit clone --depth 1 https://github.com/hoavdc/CodexKitWhat 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 | $0.00056 | $0.01160 |
| Opus 5 | $0.00028 | $0.00580 |
| Sonnet 5 | $0.00011 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
codexkit-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 2d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision Log
When to Use
- When a decision affects multiple teams or has lasting consequences
- When leadership needs an auditable trail of why choices were made
- When recurring decisions need a consistent framework
- When decisions stall due to unclear ownership or roles
Procedure
Step 1 — Frame the Decision
| Element | Description |
|---|---|
| Decision ID | DEC-YYYY-NNN |
| Title | One-line description |
| Category | Strategic / Tactical / Operational |
| Urgency | Critical (24h) / High (1 week) / Normal (2 weeks) / Low |
| Reversibility | Easy / Moderate / Difficult / Irreversible |
| Scope | Who and what is affected |
Step 2 — RAPID Roles
Assign clear decision roles:
| Role | Person | Responsibility |
|---|---|---|
| R — Recommend | [Name] | Researches, proposes recommendation |
| A — Agree | [Names] | Must agree before approval (has veto) |
| P — Perform | [Names] | Implements the decision |
| I — Input | [Names] | Provides data/perspective (no veto) |
| D — Decide | [Name] | Makes the final call (ONE person) |
Rule: Exactly one D. Multiple A/P/I are fine.
Step 3 — Options Analysis
| Criterion | Option A | Option B | Option C (Status Quo) |
|---|---|---|---|
| Cost | $50K | $30K | $0 |
| Time to implement | 3 months | 6 months | — |
| Risk | Low | Medium | High (doing nothing) |
| Alignment with strategy | High | Medium | Low |
Step 4 — Risk Assessment
| Option | Risk | Probability | Impact | Mitigation |
|---|---|---|---|---|
| A | Vendor lock-in | Medium | High | Contractual exit clause |
| B | Team capacity | High | Medium | Phase rollout |
Step 5 — Decision Record
Decision: We will proceed with Option A
Rationale: Best alignment with strategy, acceptable cost, low risk
Trade-offs accepted: Higher cost than Option B
Conditions: Must complete vendor contract review by [date]
Review date: [6 months from now]
What ships with it
1 file 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.
- 2d ago First seen · 148 lines · 56 tokens per session scan A 1e0499939a7a
codexkit-decision-log is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,160 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-08-30.
Other skills, from other repositories
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
analyzing-security
Scans code for security vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when running security scans, auditing code, or checking for OWASP issues, injection risks, or sensitive data leaks. Automatically triggered on new modules, security-related changes, or post-refactor.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
building-agent-systems
AI agent and LLM system engineering reference covering single-agent dev (ReAct, tool calling, plan-execute), multi-agent coordination (swarm, role decomposition, file locking), LLM security (prompt injection, jailbreak defense, output filtering), RAG architecture (chunking, hybrid retrieval, rerank), and prompt…