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 IvanLutsenko/awac-ai-agent-plugins --skill donegit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWrote 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/ivanlutsenko/awac-ai-agent-plugins/done)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/done"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/done.svg" alt="Measured on agentmods" 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.00027 | $0.00418 |
| Opus 5 | $0.00014 | $0.00209 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
obsidian-tracker-done 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 3d 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
Converted from Claude Code command
/done. Review and adapt: hooks and MCP tool IDs may need manual mapping for Codex.
Done Command
Moves a task to Done column on kanban board. Optionally logs actual time spent.
Arguments
- task-id (required) - Task ID number (e.g., 3)
- --project (optional) - Project name
- --actual (optional) - Actual time spent (e.g., "1h", "30m")
Examples
/done 3 --actual 1h
/done 5 --project api
/done 1
Logic
-
Парси аргументы: task-id (число), --project, --actual.
-
Определи проект:
- Если --project указан — используй его
- Если
.claude/obsidian-tracking.jsonсуществует — прочитай project оттуда - Иначе — вызови
listProjects, покажи список, спроси у пользователя
-
Если task-id не указан: Вызови
listTasksдля проекта. Покажи активные задачи (Backlog + In Progress + Review):| # | ID | Title | Status |Спроси у пользователя номер.
-
Вызови MCP tool:
mcp__plugin_obsidian_tracker_obsidian__updateTask с параметрами: project, taskId, status="Done", actual -
Выведи:
TASK-{id} done! {from} → Done Actual: {actual} -
Auto-update tracking: Если
.claude/obsidian-tracking.jsonсуществует — добавь"Completed TASK-{id}"в actions.
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.
- 3d ago First seen · 59 lines · 27 tokens per session scan A 20b233663e03
obsidian-tracker-done is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 418 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
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.