Borrowing it
Nothing to install: this file belongs to beyondeye/aitasks. 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/beyondeye/aitasks/main/.opencode/commands/aitask-resume.mdgit clone --depth 1 https://github.com/beyondeye/aitasksWrote 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/beyondeye/aitasks/aitask-resume)<a href="https://agentmods.dev/commands/beyondeye/aitasks/aitask-resume"><img src="https://agentmods.dev/badge/commands/beyondeye/aitasks/aitask-resume.svg" alt="Measured on agentmods" 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.00026 | $0.00251 |
| Opus 5 | $0.00013 | $0.00125 |
| Sonnet 5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
aitask-resume 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 4d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 4d ago First seen · 23 lines · 26 tokens per session scan A 83bc229fc943
aitask-resume is a command published in the GitHub repository beyondeye/aitasks (8 stars, last pushed yesterday), with no licence file. It adds 26 tokens to every session and 251 once invoked, about $0.0001 per session on Opus 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-03.
Other commands, from other repositories
maintainer-review-code-review
Review the PR for code quality, CLAUDE.md compliance, project conventions, and bugs (Pi-tuned).
maintainer-review-synthesize
Synthesize findings from all review aspects into a single maintainer-ready review report (Pi-tuned).
maintainer-review-comment-quality
Review the PR's added/modified comments and docstrings for accuracy, value, and long-term maintainability (Pi-tuned).
maintainer-review-error-handling
Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).
review-synthesize
Produce one evidence-based verdict, write the review report humans read, and publish it when the scope is a PR. You are read-only: never modify project files or commit; your only write outside the artifacts directory is the PR comment below. Read-only extends past the repository: a falsifying command creates its own…
review-seams
Hunt one defect: a type is missing at a seam, and something downstream pays for it — a parser that mis-reads, a hand-synced copy of a set, type, or table whose owner it could import or derive from, a second route that skips the validator, a value that silently loses fields across a re-entry. Read-only: never modify…