Borrowing it
Nothing to install: this file belongs to sflandergan/agentic-coding. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sflandergan/agentic-coding/main/.agents/skills/agent-implementation/SKILL.mdgit 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/agent-implementation)<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/agent-implementation"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/agent-implementation/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/agent-implementation"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/agent-implementation.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.00021 | $0.00484 |
| Opus 5.5 | $0.00008 | $0.00194 |
| Sonnet 5.5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
agent-implementation 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 2mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Implementation — Self-Maintenance
Controller orchestration for implementing plans against this toolkit repo.
Core principle: Fresh implement-task worker per task + verification gate = quality commits.
Continuous execution: Execute all tasks from the plan without routine pauses between tasks. Stop for: BLOCKED status, genuine ambiguity, or all tasks complete.
The Process
- Extract one task with enough context for isolated execution.
- Give the worker the full task text, relevant spec/plan paths, and current branch state.
- Review the worker report and diff before moving on.
- Fix and re-review every open issue before marking the task complete.
- Run final verification before any completion or push claim.
Worker Contract
The implement-task worker:
- Implements exactly one task
- Creates or modifies only the files specified
- Runs task-level verification on changed files (shellcheck, bash -n, codespell on changed prose/markdown files)
- Commits with a focused message
- Reports status: DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED
- Does not push, create PRs, or dispatch other workers
Handling Worker Status
- DONE: Verify the diff, move to next task.
- DONE_WITH_CONCERNS: Read concerns. If about correctness, address before continuing.
- NEEDS_CONTEXT: Provide missing context and re-dispatch.
- BLOCKED: Assess: context problem → provide more; plan wrong → escalate to human.
Treat every worker escalation as actionable. If the worker said it's stuck, something needs to change.
Operating Rules
- Start from a scoped branch.
- Run the relevant verification before status claims and before moving to the next task.
- Resolve correctness issues before continuing.
- Dispatch workers sequentially by default; use parallel workers only for independent tasks touching disjoint files.
- Give each worker the task text, relevant context, and branch state.
Completion
After all tasks complete and final verification passes:
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.
- 2mo ago First seen · 58 lines · 21 tokens per session scan A 22773ba795f7
agent-implementation is a skill published in the GitHub repository sflandergan/agentic-coding (4 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 484 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-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…