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 duc01226/EasyPlatform --skill task-trackgit clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/task-track)<a href="https://agentmods.dev/skills/duc01226/easyplatform/task-track"><img src="https://agentmods.dev/badge/skills/duc01226/easyplatform/task-track/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/duc01226/easyplatform/task-track"><img src="https://agentmods.dev/badge/skills/duc01226/easyplatform/task-track.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.00048 | $0.00764 |
| Opus 5.5 | $0.00019 | $0.00306 |
| Sonnet 5.5 | $0.00010 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
task-track 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex compatibility note:
- Invoke
$skill-name: load the registered.agents/skills/<name>/SKILL.mdand execute it with Codex tools; no separateSkilltool or Claude mode switch is needed. Author.claude/**; mirrors are generated.- Track steps before execution and keep progress/evidence current. Explicit skill requests execute their protocol. Use the native question tool for required questions.
- Map foreign tool names to available host capabilities. A name mismatch needs no approval; an actually unavailable required capability stops with its step/evidence and a user question before adaptation.
- Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required
spawn_agentsubagent(s) for that task.- Preserve protocol order unless the user approves a deviation. Workflows use
$start-workflow: gates stay fixed; other steps may flex with logged reasons and evidence.
Quick Summary
Goal: Support the selected project's tracker conventions or the portable work engine through one
explicit entry point. Read only the selected route's reference before acting. These modes are
skill purposes, not CLI flags; never pass --mode=guide to the engine command.
| Invocation | Read and follow |
|---|---|
--mode=guide |
Project guide: discover the selected checkout's root-linked work-tracking instruction and use its documented mechanism |
Bare invocation, or --mode=inspect|maintain|link|lifecycle|verify|accept|report|serve |
Engine protocol: preserve the bare inspect default and existing operation safeguards |
| Any other mode | Refuse without an operation |
Choose by the invocation, never by the presence of a tracker folder, root pointer or configured
engine. When both exist, explicit guide uses project instructions; an old mode still uses the
engine protocol. Project prohibitions and unsupported engine capabilities remain binding;
never switch routes to bypass a refusal. Guide mode does not initialize, enroll or migrate a
tracker, and does not require portable-engine configuration.
Honor the active host's Run/Skip and disabled-selection controls. This skill remains manual-only; a named authorized invocation remains usable. Invocation supplies guidance, not permission for assignment, acceptance, publication or other actions beyond the user's request.
What ships with it
29 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.
- agents/openai.yaml 162 B
- assets/app.js 239 KB runs code
- assets/favicon.svg 365 B
- assets/fonts/OFL-red-hat-display.txt 4.4 KB
- assets/fonts/OFL-red-hat-mono.txt 4.4 KB
- assets/fonts/OFL-red-hat-text.txt 4.4 KB
- assets/fonts/red-hat-display-latin-ext-wght-normal.woff2 14 KB
- assets/fonts/red-hat-display-latin-wght-normal.woff2 30 KB
- assets/fonts/red-hat-mono-latin-ext-wght-normal.woff2 11 KB
- assets/fonts/red-hat-mono-latin-wght-normal.woff2 22 KB
- assets/fonts/red-hat-text-latin-ext-wght-normal.woff2 13 KB
- assets/fonts/red-hat-text-latin-wght-normal.woff2 29 KB
- assets/fonts/SOURCE.txt 574 B
- assets/index.html 2.5 KB
- assets/style.css 80 KB
- lib/browser-launch.cjs 5.1 KB runs code
- lib/package-setup.cjs 7.9 KB runs code
- lib/report-view.cjs 137 KB runs code
- lib/shared-snapshot.cjs 16 KB runs code
- lib/terminal-launch.cjs 6.4 KB runs code
- lib/workspace-server.cjs 17 KB runs code
- package.json 280 B
- references/engine-protocol.md 27 KB
- references/integration-guide.md 22 KB
- references/manual-operations.md 73 KB
- references/project-guide.md 3.1 KB
- scripts/task-track.cjs 21 KB runs code
- tests/browser-support.cjs 12 KB runs code
- tests/workspace-browser.test.cjs 417 KB runs code
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 · 52 lines · 48 tokens per session scan A 948d09d68b90
task-track is a skill published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 764 once invoked, about $0.0002 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-10-18.
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,"…