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-startgit 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-start)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/track-start"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/track-start.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.00025 | $0.00445 |
| Opus 5 | $0.00013 | $0.00222 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade B, and why
obsidian-tracker-track-start 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 yesterday.
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-start. Review and adapt: hooks and MCP tool IDs may need manual mapping for Codex.
Track Start Command
Включает автоматический трекинг текущей сессии для логирования в Obsidian.
Step 0: Check Configuration
Вызови MCP tool:
mcp__plugin_obsidian_tracker_obsidian__getConfig
Если initialized: false: выполни инициализацию как в /projects команде.
Step 1: Check existing tracking
cat .claude/obsidian-tracking.json 2>/dev/null || echo "NO_TRACKING"
Если трекинг уже активен:
⚠️ Трекинг уже активен для проекта: {project}
Используй /track-stop чтобы завершить текущий.
Останови выполнение.
Step 2: Resolve project
Если project-name указан: используй его.
Если project-name НЕ указан:
- Получи список проектов:
mcp__plugin_obsidian_tracker_obsidian__listProjects - Спроси через AskUserQuestion какой проект трекать.
Step 3: Get goal
Спроси через AskUserQuestion:
- "Какая цель этой сессии?" (текстовый ввод)
Step 4: Create tracking marker
Создай трекинг-файл через скрипт:
plugins/obsidian-tracker/scripts/start-tracking.sh "{project-name}" "{goal}"
Step 5: Confirm
🟢 Трекинг включён
- Проект: {project}
- Цель: {goal}
- Время: {started}
Твои действия будут автоматически записываться.
Используй /track-stop или /clear для сохранения в Obsidian.
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.
- yesterday First seen · 71 lines · 25 tokens per session scan B 591c2a13e467
obsidian-tracker-track-start is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 445 once invoked, about $0.0001 per session on Opus 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.