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 arozumenko/sdlc-skills --skill completing-a-taskgit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote 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/arozumenko/sdlc-skills/completing-a-task)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/completing-a-task"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/completing-a-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/arozumenko/sdlc-skills/completing-a-task"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/completing-a-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 46 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 46 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 46 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 46 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00057 | $0.01187 |
| Opus 5.5 | $0.00023 | $0.00475 |
| Sonnet 5.5 | $0.00011 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
completing-a-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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Completion Protocol
When you are assigned a task — via a host-native subagent call, a PM message, a tracker ticket, or any routed work — a task is only complete when all five steps have happened, in order. Writing the code is step 1, not step 5. If you stop at step 1 and hand a diff back to your caller, you have left the task unfinished.
Platform & systems — translate before running
The commands below are written in GitHub gh form as the reference.
Read scout's discovery first and translate:
.agents/workflow.md§ Git host — your code host and its CLI: GitHubgh, GitLabglab, Bitbucketbb, Azure DevOpsaz repos, Giteatea. "PR" below means PR or MR (your host's unit of change)..agents/profile.md§ Project systems — where tickets live (github-issues / jira / gitlab-issues / azure-boards / linear). Step 4 comments on the ticket there, which may differ from the code host.
The five steps are identical on every platform — only the commands change. If scout hasn't recorded a host/tracker, ask before assuming GitHub.
1. Code verified locally
Tests pass, type/syntax checks clean, lint clean if configured, manual check where applicable. If this step fails, the task is not done — fix it or report the blocker.
Language-specific verification commands:
- JS/TS:
npx tsc --noEmit,npx eslint <path>,npm test/npx jest/npx vitest - Python:
python -m py_compile <file>,pytest -x -q,mypyif configured - Go:
go build ./...,go vet ./...,go test ./... - Rust:
cargo check,cargo clippy,cargo test
"I wrote the code and it compiles" is not verification. Run the thing.
2. Committed on a feature branch
Never commit directly to main or master. Always branch first:
git checkout -b <type>/<short-description>
git commit with a message that explains why, not just what. Small, focused
commits are better than one giant blob.
3. Pushed and PR/MR opened
What ships with it
1 file 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 · 146 lines · 57 tokens per session scan A 400c079f453a
completing-a-task is a skill published in the GitHub repository arozumenko/sdlc-skills (25 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 1,187 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-08-30.
Other skills, from other repositories
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-pause-work
Create context handoff when pausing work mid-phase.
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.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.