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 paralleldrive/aidd --skill aidd-loggit clone --depth 1 https://github.com/paralleldrive/aiddWrote 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/paralleldrive/aidd/aidd-log)<a href="https://agentmods.dev/skills/paralleldrive/aidd/aidd-log"><img src="https://agentmods.dev/badge/skills/paralleldrive/aidd/aidd-log/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/paralleldrive/aidd/aidd-log"><img src="https://agentmods.dev/badge/skills/paralleldrive/aidd/aidd-log.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.00041 | $0.00451 |
| Opus 5.5 | $0.00016 | $0.00180 |
| Sonnet 5.5 | $0.00008 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
aidd-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 1mo 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.
What it actually says
log
Act as a senior software engineer to log completed epics using the following template:
## $date
- $emoji - $epicName - $briefDescription
What to Log
LOG ONLY COMPLETED EPICS - Focus on completed epics that represent significant user-facing value:
- ✅ Epic Completions: Major feature releases, tool creation, system implementations
- ✅ User-Impacting Changes: New capabilities, workflows, or developer experience improvements
- ✅ Architecture Decisions: Significant refactoring, new patterns, or system redesigns
DO NOT LOG:
- ❌ Config file changes (.json, .config updates)
- ❌ File organization/moves (directory restructuring)
- ❌ Minor bug fixes (unless epic-level)
- ❌ Documentation updates (unless epic-level)
- ❌ Dependency updates
- ❌ Internal refactoring
- ❌ Test additions/changes
- ❌ Meta-work (logging, planning, etc.)
Emojis
Use the following emoji to represent the epic type:
- 🚀 - new feature
- 🐛 - bug fix
- 📝 - documentation
- 🔄 - refactor
- 📦 - dependency update
- 🎨 - design
- 📱 - UI/UX
- 📊 - analytics
- 🔒 - security
Constraints { Always use reverse chronological order. Add most recent epics to the top. Keep descriptions brief (< 50 chars). Focus on epic-level accomplishments, not implementation details. Never log meta-work or trivial changes. Omit the "epic" from the description. }
gitChanges() { git add . git --no-pager diff --cached }
planChanges() { Check the plan diff to detect recently completed plan tasks. }
detectChanges() { gitChanges |> planChanges |> logDetectedChanges }
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.
- 1mo ago First seen · 70 lines · 41 tokens per session scan A 16fbe6c2a282
aidd-log is a skill published in the GitHub repository paralleldrive/aidd (385 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 451 once invoked, about $0.0002 per session on Opus 5.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
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.
deploy-agent
Use when ship code through controlled pipeline with verification gates and rollback plans.
github-repo-management
Clone, create, fork repos; manage remotes, releases.
chinese-commit-conventions
A Chinese-language reference for writing commit messages and changelogs, which record code changes and releases.
deploy-pipeline-runbook
Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.
secret-leak-preflight
Use when about to commit, push, or publish -- staged changes touch config or environment files, generated artifacts (relay sessions, logs, build output) are being added, or the session handled credentials even indirectly.