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 lacvietanh/akidevrule --skill akidevsync-notesgit clone --depth 1 https://github.com/lacvietanh/akidevruleWrote 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/lacvietanh/akidevrule/akidevsync-notes)<a href="https://agentmods.dev/skills/lacvietanh/akidevrule/akidevsync-notes"><img src="https://agentmods.dev/badge/skills/lacvietanh/akidevrule/akidevsync-notes/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/lacvietanh/akidevrule/akidevsync-notes"><img src="https://agentmods.dev/badge/skills/lacvietanh/akidevrule/akidevsync-notes.svg" alt="Reviewed on agentmods" width="80" 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.00137 | $0.01126 |
| Opus 5 | $0.00068 | $0.00563 |
| Sonnet 5 | $0.00027 | $0.00225 |
| Haiku 4.5 | $0.00014 | $0.00113 |
Grade A, and why
akidevsync-notes 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
akidevsync-notes — edit a project's Aki-Dev-Sync task file safely
The Aki-Dev-Sync app stores every project's task list at <project>/.akidevsync/notes.json (schema: about, schema, notes, tasks[], updated_at; each task has id, title, detail, done, pin, wish, created_at, updated_at in epoch-ms). The file is normally gitignored (.akidevsync/ — the app excludes it from PUSH/PULL by default too), so edits here are local-only and never show up in git diff.
Never hand-edit the JSON with the Edit tool. The app itself reads/writes this file, so any mutation must match its exact formatting (2-space indent, ensure_ascii=False so Vietnamese text stays literal, alphabetical per-task key order, a trailing newline) or the next diff a human looks at gets noisy for no reason. Always go through the bundled script:
python3 ~/.claude/skills/akidevsync-notes/scripts/notes_cli.py <path-to-notes.json> <command> [args]
(On Antigravity/Codex/Kiro/Grok, substitute that CLI's skills root — see ~/.aki/akidevrule/.source-repo's README.md for the list of sync targets.)
Locating the file
find <project-root> -maxdepth 2 -name notes.json -path '*/.akidevsync/*' (or just check <cwd>/.akidevsync/notes.json). If it does not exist, the project has never opened in Aki-Dev-Sync, or task notes were never migrated — do not create one uninvited. Only run ... init when the user explicitly asks to start tracking tasks for a project that doesn't use the app.
Commands
list [--pin] [--done] [--pending] [--wish] [--detail] # --detail also prints each task's detail body
add "<title>" [--detail "<text>"] [--pin] [--wish]
set <task-id> [--done true|false] [--pin true|false] [--wish true|false] [--title "<t>"] [--detail "<t>"]
delete <task-id> # permanent — confirm with the user first
note "<text>" # replaces the project-wide notes field (not a task)
init # only if the user explicitly wants a new file
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.
- 9d ago First seen · 49 lines · 137 tokens per session scan A 7f9bb4daa791
akidevsync-notes is a skill published in the GitHub repository lacvietanh/akidevrule (9 stars, last pushed yesterday), licensed MIT. It adds 137 tokens to every session and 1,126 once invoked, about $0.0007 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
starfleet
Fleet coordination — comms, concurrency, task capture, and starfleetctl CLI. Load when handling inter-ship messages, setting up parallel work, capturing tasks, or running starfleetctl commands.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…
spec-coherence-check
Sweep all active OpenSpec proposals for staleness, conflicts, and obsolescence against the current codebase and archived changes. Use when proposals may be outdated, when checking cross-proposal conflicts, or before starting a batch of implementations. Produces a gap-analysis report, updates a priority queue file, and…