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 taskgit 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/task)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/task"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/task/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/task"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/task.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.00029 | $0.00875 |
| Opus 5.5 | $0.00012 | $0.00350 |
| Sonnet 5.5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
obsidian-tracker-task 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 14d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Converted from Claude Code command
/task. Review and adapt: hooks and MCP tool IDs may need manual mapping for Codex. Helper scripts ship in this skill's ownscripts/directory. Replace<this skill directory>with the path Codex reported when it loaded this skill — a bare relative path would resolve against the repository under review instead.
Task Command
Creates a task with auto-increment ID and adds to kanban board (Backlog column).
Step 0: Check Configuration
Вызови mcp__plugin_obsidian_tracker_obsidian__getConfig.
Если initialized: false — выполни инициализацию как в /projects.
Arguments
- title (required) - Task title (first quoted string or positional arg)
- --project (optional) - Project name
- --priority (optional) - critical|high|medium|low (default: medium)
- --effort (optional) - Time estimate (e.g., "2h", "1d", "30m")
- --assignee (optional) - Assignee name
- Любые дополнительные --key value передаются в extra (расширяемая YAML-схема)
Examples
/task "Add rate limiting" --project api --priority high --effort 2h
/task "Fix login bug"
/task "Update docs" --project myapp --effort 30m --client Acme
Logic
-
Парси аргументы из пользовательского ввода.
-
Если --project не указан: Вызови
listProjects, покажи нумерованный список, спроси у пользователя. -
Если title не указан: Спроси через AskUserQuestion.
-
Определи тип информации:
- Если пользователь даёт actionable задачу (что-то нужно СДЕЛАТЬ) — это TASK, используй
addTask. - Если пользователь даёт справочную информацию, контекст, описание, заявку, требования — это КОНТЕКСТ ПРОЕКТА, используй
updateProjectс параметромcontext. - Примеры TASK: "Подготовить презентацию", "Пофиксить баг", "Добавить фичу"
- Примеры КОНТЕКСТ: "Вот моя заявка на конференцию: ...", "Требования от заказчика: ...", "Описание проекта: ..."
- Если не уверен — спроси пользователя: "Это задача или контекст проекта?"
- Если пользователь даёт actionable задачу (что-то нужно СДЕЛАТЬ) — это TASK, используй
-
Собери extra-поля: все --key value кроме project/priority/effort/assignee.
What ships with it
2 files 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.
- 14d ago Changed · +7 lines 367819080bb2
- 1mo ago First seen · 76 lines · 29 tokens per session scan A 5bada4bccca7
obsidian-tracker-task is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 875 once invoked, about $0.0001 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-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,"…