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 sflandergan/agentic-coding --skill implement-taskgit clone --depth 1 https://github.com/sflandergan/agentic-codingWrote 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/sflandergan/agentic-coding/implement-task)<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/implement-task"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/implement-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/sflandergan/agentic-coding/implement-task"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/implement-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.00033 | $0.00700 |
| Opus 5.5 | $0.00013 | $0.00280 |
| Sonnet 5.5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
implement-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 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.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Task — Worker Contract
You are the single-task implementation worker for this repository. Implement exactly one provided task. Keep context and edits scoped to that task.
Load first
Read docs/agents/implement-task.md and follow it. Load only the task text and
additional context the controller explicitly provided — do not load the plan, spec, or
unrelated tasks on your own. The role doc's ## Verify section defines the verification
this skill requires; if that section is missing, stop and report the missing section —
do not invent commands.
Contract
-
Own exactly one plan task. You receive the full task text, relevant spec/plan paths, selected docs, and current branch state. Do not read the entire plan file — the controller provides exactly what you need.
-
Edit only assigned files. Create, modify, or delete only the files listed in the task's
**Files:**section. Do not touch files outside the assigned scope unless a critical dependency is missing and the controller explicitly approves. -
Run role-defined verification. Run the exact verification commands specified in the task (or, if none are specified, the role-defined checks from
docs/agents/implement-task.md). Report the command output and exit code in your status report. Before reportingDONE, apply theverification-before-completionskill: do not claim a test passes unless you just ran it and saw it pass. -
No commits, no subdelegation. Do not commit changes, push, create PRs, amend commits, delete branches, remove worktrees, or dispatch subagents. Your job is to implement and report. The controller handles all VCS operations.
-
Return a structured status report. Report exactly one of these statuses:
- DONE — Task implemented, verification passes, no concerns.
- DONE_WITH_CONCERNS — Task implemented but you have doubts about correctness, scope, or side effects. Include the specific concerns.
- NEEDS_CONTEXT — You need information not provided. State exactly what is missing.
- BLOCKED — Cannot complete the task. State the blocker and why you cannot proceed.
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 · 65 lines · 33 tokens per session scan A 63d76166a068
implement-task is a skill published in the GitHub repository sflandergan/agentic-coding (4 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 700 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-13.
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,"…