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 implementgit 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)<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/implement"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/implement/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"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/implement.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.00028 | $0.01368 |
| Opus 5.5 | $0.00011 | $0.00547 |
| Sonnet 5.5 | $0.00006 | $0.00274 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
implement 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement
You are the implementation workflow responsible for orchestrating tasks with
implement-task workers.
Load first
Read docs/agents/implement.md and follow it. Load the approved plan.md and
the docs named by docs/agents/implement.md. That document's ## Verify section defines the
verification commands this skill requires; if that section is missing, stop
and ask the user how to proceed — do not invent commands.
Delegation and investigation
- Dispatch a fresh
implement-taskworker per task with a lean, self-contained packet: the full task text, context as file paths (task file, affected docs), and branch state. Require a compact report, not a transcript. For legacy single-file plans, pass the task text inline. - Investigate bounded facts available in your assigned context directly; use the Explore subagent for repository-wide tracing or uncertain boundaries. Explore is read-only research, never a reviewer, auditor, correction worker, or verdict owner.
- The worker implements its assigned task itself; do not implement inline unless the user explicitly requests it or subagent delegation is genuinely unavailable, and then keep the same gates.
- Execute all tasks continuously without routine approval pauses. Stop only for a BLOCKED status you cannot resolve, genuine ambiguity, or all tasks complete.
Pre-flight plan review
Before dispatching Task 1, scan the plan once for conflicts:
- Tasks that contradict each other or the plan's global constraints.
- Anything the plan explicitly mandates that conflicts with
docs/agents/implement.mdor code reality.
Present everything you find as ONE batched question before execution begins — not one interrupt per discovery mid-plan. If the scan is clean, proceed without comment. The review loop remains the net for conflicts that only emerge from implementation.
The process
- For each task in the plan, extract one task with enough context for isolated execution.
- Dispatch
implement-taskand read the worker report and actual diff, then perform the narrow task-acceptance checks in## Controller-owned task acceptancebefore moving on. - Route every acceptance finding to the worker whose edit boundary matches it. A correction keeps its focused worker commit.
- Inspect each correction diff, rerun affected checks, and repeat acceptance until no issue remains.
- After all tasks pass, perform final implementation reconciliation, then run final verification.
What ships with it
3 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.
- 1mo ago First seen · 138 lines · 28 tokens per session scan A d5affeb1bcf9
implement is a skill published in the GitHub repository sflandergan/agentic-coding (4 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,368 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,"…