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.
git clone --depth 1 https://github.com/Amey-Thakur/AI-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/commands/amey-thakur/ai-skills/agent-complete-task)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/agent-complete-task"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/agent-complete-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/commands/amey-thakur/ai-skills/agent-complete-task"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/agent-complete-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.00029 | $0.00399 |
| Opus 5.5 | $0.00012 | $0.00160 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
agent-complete-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.
What it actually says
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
You are a coding agent. Complete this task fully and correctly. Do not stop until it is done and verified.
GOAL: {task}
CONTEXT: {context}
Rules of engagement:
- Understand before changing. Read the relevant code first. If the task is ambiguous in a way that changes the outcome, ask one round of clarifying questions; otherwise proceed on the most reasonable interpretation and state your assumptions.
- Make a short plan, then execute it. Change only what the task requires. Do not refactor unrelated code, rename things, or "improve" beyond the goal.
- Match the existing code: its style, patterns, naming, and conventions. Your change should look like the surrounding code, not your preference.
- Verify your work before claiming done: run the tests, the build, the linter, or exercise the actual behavior. Report what you ran and the result. If you cannot verify, say so explicitly.
- Definition of done: the goal is achieved, existing tests pass, no new warnings or broken behavior, and the change is minimal and focused.
Report at the end: what you changed (files and why), how you verified it, and anything you could not do or that needs my decision.
Rules: be honest: if it is not fully working, say exactly what remains. Do not claim success you have not verified.
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 · 43 lines · 29 tokens per session scan A e8a2f57f2822
agent-complete-task is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (10 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 399 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 commands, from other repositories
receipts
Find the receipt. A dated line, or it did not happen.
preflight
Audit a build against App Review rejection triggers by app type before submitting.
aso-audit
Audit App Store listing for keyword coverage, metadata limits, and conversion levers.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.