Borrowing it
Nothing to install: this file belongs to okfriansyah-moh/ares. 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/okfriansyah-moh/ares/main/.ai/skills/task-implementation/SKILL.mdgit clone --depth 1 https://github.com/okfriansyah-moh/aresWrote 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/okfriansyah-moh/ares/task-implementation)<a href="https://agentmods.dev/skills/okfriansyah-moh/ares/task-implementation"><img src="https://agentmods.dev/badge/skills/okfriansyah-moh/ares/task-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/okfriansyah-moh/ares/task-implementation"><img src="https://agentmods.dev/badge/skills/okfriansyah-moh/ares/task-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.00000 | $0.00483 |
| Opus 5.5 | $0.00000 | $0.00193 |
| Sonnet 5.5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
task-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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Implement one planned task at a time from docs/PLAN.md while preserving architecture, scope, and validation discipline.
Inputs
docs/architecture.mdfor system boundaries and non-negotiable design decisions.docs/PLAN.mdfor task order, dependencies, required files, coding standards, and validation steps.- Relevant
.ai/instructions/, agents, skills, and prompts for repository-specific guidance. - Current code, tests, and git status for implementation context.
Process
- Read the full target task in
docs/PLAN.md, including its goal, files, coding standards, validation, and prompt context. - Check the dependency graph and task summary before starting; only work on the selected task and its direct prerequisites if they are missing.
- Treat the task boundary as the listed goal plus listed files and validation criteria. Do not add future task behavior, new architecture, or speculative abstractions.
- Inspect existing package patterns before editing. Keep changes small, idiomatic, and aligned with current boundaries.
- Implement production code and focused tests together. Avoid placeholders, TODOs, or stubs unless the plan explicitly calls for temporary scaffolding.
- If the task reveals a plan gap, make the smallest implementation-compatible choice and document the issue for review rather than expanding scope.
Validation
- Run the task-specific validation commands from
docs/PLAN.md. - Before finishing a task, run:
go build ./...
go vet ./...
staticcheck ./...
go test -race -count=1 ./...
govulncheck ./...
- Confirm all required files were created or updated with non-stub implementation.
- Confirm no future task files or behaviors were introduced.
- Confirm failures are fixed before continuing, or clearly report any unavailable tool or external blocker.
Anti-Patterns
- Implementing multiple plan tasks in one pass.
- Adding runtime, network, database, frontend, plugin, or marketplace behavior in v1.
- Redesigning architecture to make the current task easier.
- Creating abstractions before repeated complexity exists.
- Skipping race tests, vet, staticcheck, or vulnerability checks after implementation.
- Preparing a commit with unrelated changes, generated noise, failing tests, or unreviewed scope drift.
- Committing without checking
git status, reviewing the diff, and using a task-scoped commit message.
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 · 47 lines · 0 tokens per session scan A bbbc47d6a396
task-implementation is a skill published in the GitHub repository okfriansyah-moh/ares (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 483 tokens. 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
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
codex-skin-pack-installer
Install Codex themes and Codex skin packs with npx skills. Use this skill when a user wants Codex to find, download, validate, apply, switch, remix, or restore Codex desktop themes such as caishen-readable, caishen-lite, mythic-guardian-noir, global-founder-bright, export-night, or caishen-max. It stages verified…
om-build-workflow
Build or extend standalone business workflows, activities, event triggers, durable user tasks, compensation, output paths, idempotency, and live progress. Use for "add workflow", "custom activity", "CALLAPI", "approval task", "workflow progress", or "zbuduj workflow".
community
Use when building or running a persistent two-way community space — Discord, Telegram, Circle: platform choice, structure, onboarding, native→bot→human moderation, rituals, growth loops, health metrics. NOT churn of paying product customers (that is retention), NOT broadcast email (that is newsletter), NOT one live…
memstack-automation-n8n-workflow-builder
Use this skill when the user says 'n8n workflow', 'build a workflow', 'automation workflow', 'connect services', or needs visual workflow design with node mapping, data transformations, and error handling for n8n. Do NOT use for standalone webhook endpoints or cron jobs.