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.00113 | $0.01102 |
| Opus 5.5 | $0.00045 | $0.00441 |
| Sonnet 5.5 | $0.00023 | $0.00220 |
| Haiku 4.5 | $0.00011 | $0.00110 |
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 27d 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.
- 27d ago Changed · -24 tokens per session 05cd304af10f
- 1mo ago First seen · 49 lines · 137 tokens per session scan A 7f9bb4daa791
akidevsync-notes is a skill published in the GitHub repository lacvietanh/akidevrule (10 stars, last pushed 4d ago), licensed MIT. It adds 113 tokens to every session and 1,102 once invoked, about $0.0005 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-31.
Other skills, from other repositories
starfleet-tasks
Task capture, task lifecycle, dashboard topics, and reports via starfleetctl. Load when capturing, working on, or reporting a task, and for all dashboard access.
starfleet
Fleet coordination core — comms, board status, concurrency/isolation, and pointers to the themed starfleet- skills. Load when handling inter-ship messages, checking the board, or unsure which starfleet skill applies.
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-access
Map, suggest and request the folder access a project needs: map (read-only report), suggest (draft .pi/access.json from this project's grants), provision (submit it for line-by-line operator approval). Use on "what folders can this project reach", "set up folder access", "write .pi/access.json", repeated folder access…
starfleetctl-dev
Developing and deploying the starfleetctl source itself — claim protocol, make, bootstrap, daemon restarts in the right order, end-to-end verification. Load before editing anything in a starfleetctl source checkout, before running starfleet-bootstrap, or when a web/plugin change 'is done' but the fleet does not see it.
starfleet-sessions
Ship session and workspace management — spawning ships, session attach/stop, git worktrees, web console, deployment. Load when launching/administering ships or managing the fleet web console.