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 track-statusgit 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/track-status)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/track-status"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/track-status/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/ivanlutsenko/awac-ai-agent-plugins/track-status"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/track-status.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.00021 | $0.00261 |
| Opus 5.5 | $0.00008 | $0.00104 |
| Sonnet 5.5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade B, and why
obsidian-tracker-track-status scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/obsidian-tracking.json 2>/dev/null || echo "NO_TRACKING" What it actually says
Converted from Claude Code command
/track-status. Review and adapt: hooks and MCP tool IDs may need manual mapping for Codex.
Track Status Command
Показывает текущий статус трекинга.
Step 1: Check tracking
cat .claude/obsidian-tracking.json 2>/dev/null || echo "NO_TRACKING"
Если NO_TRACKING:
🔴 Трекинг не активен
Используй /track-start [project] чтобы начать.
Если файл существует:
Прочитай JSON и выведи:
🟢 Трекинг активен
- Проект: {project}
- Цель: {goal}
- Начат: {started}
- Продолжительность: {now - started}
- Actions записано: {actions.length}
Actions:
{actions.map(a => " - " + a).join("\n")}
Команды:
- /track-stop — сохранить и завершить
- /clear — автоматически сохранит и завершит
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 · 47 lines · 21 tokens per session scan B 5288ab9bd009
obsidian-tracker-track-status is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 261 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…