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 aka-kika/akakika-skills --skill old-project-auditgit clone --depth 1 https://github.com/aka-kika/akakika-skillsWrote 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/aka-kika/akakika-skills/old-project-audit)<a href="https://agentmods.dev/skills/aka-kika/akakika-skills/old-project-audit"><img src="https://agentmods.dev/badge/skills/aka-kika/akakika-skills/old-project-audit/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/aka-kika/akakika-skills/old-project-audit"><img src="https://agentmods.dev/badge/skills/aka-kika/akakika-skills/old-project-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 130 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00181 | $0.01832 |
| Opus 5 | $0.00090 | $0.00916 |
| Sonnet 5 | $0.00036 | $0.00366 |
| Haiku 4.5 | $0.00018 | $0.00183 |
Grade A, and why
old-project-audit 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 12d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Old Project Audit
An audit for things that already exist. Stale tools rot in a way fresh ones can't — the data model drifts, old scripts keep pointing at live data, and the thing sits in limbo because nobody made the call. This forces the call.
If the thing you're auditing is brand new and not yet built, run it through new-project-gate first. This skill is for things already on disk that may have stopped earning their keep.
Verdict at a glance
| Checkpoint 4 failed + unguarded → not KEEP | Checkpoint 3 failed → MERGE | Checkpoint 1 or 2 failed → ARCHIVE | Otherwise → KEEP |
|---|---|---|---|
| Resolve the footgun or archive | Two tools, one job — collapse it | Stopped earning the slot it occupies | Keep as-is, re-audit later |
[x] = healthy · [ ] = failed · [~] = unsure / needs the human
How to run it
Walk the six checkpoints in order. For each one:
- Concise why — one line on what this checkpoint protects against.
- 1-2 line answer — verdict for this project, holding both lenses. If they disagree, say so.
- Mark the check —
[x][ ]or[~].
Checkpoint 4 (footgun) is non-negotiable. If it fails and is unguarded, the verdict cannot be KEEP — a tool that can silently clobber live data is a liability regardless of how useful it is.
The checkpoints
1. Still solving a real problem Does the original problem still exist, or did the workflow move past it?
- Agent lens: is anything still calling this, or was the need absorbed elsewhere?
- Human lens: have I reached for it in the last week or month, or am I keeping it out of sentiment?
2. Earning its keep Use vs maintenance ratio. Cost of the tail it drags.
- Agent lens: what does it cost to keep legible and running — deps, schema drift, breakage surface?
- Human lens: is upkeep bigger than value; does it nag when I see it in the folder?
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.
- 12d ago First seen · 138 lines · 181 tokens per session scan A 49152451a4d3
old-project-audit is a skill published in the GitHub repository aka-kika/akakika-skills (10 stars, last pushed 2d ago), licensed MIT. It adds 181 tokens to every session and 1,832 once invoked, about $0.0009 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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.