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 agentmods add commands/dork-labs/dorkos/backfillgit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/backfill)<a href="https://agentmods.dev/commands/dork-labs/dorkos/backfill"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/backfill.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 | $0.00011 | $0.00843 |
| Opus 5 | $0.00005 | $0.00421 |
| Sonnet 5 | $0.00002 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00084 |
Grade A, and why
backfill 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 3d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Backfill
Find commits since the last tag (or a specified tag) that have no fragment yet in changelog/unreleased/, and propose one fragment per missing change. Never edits CHANGELOG.md — only /system:release compiles fragments into it (see changelog/README.md).
Backed by .claude/scripts/changelog_backfill.py (--dry-run / --json / --apply); --apply writes the fragment files.
Arguments
$ARGUMENTS- Optional: specific tag to compare from, or--dry-run- (no argument) - Compare from latest tag
v0.2.0- Compare from specified tag--dry-run- Show proposed entries without applying
Process
Step 1: Determine Base Tag
# Use argument if provided, otherwise latest tag
TAG="${1:-$(git describe --tags --abbrev=0 2>/dev/null)}"
echo "Comparing from: $TAG"
If no tags exist, report and stop.
Step 2: Get Commits Since Tag
git log $TAG..HEAD --oneline --no-merges
Step 3: Filter and Categorize
Process each commit line:
Include (conventional commit types):
feat:/feat(scope):-> Addedfix:/fix(scope):-> Fixedrefactor:/refactor(scope):-> Changedperf:/perf(scope):-> Changed
Skip (not user-facing):
chore:/ci:/test:/docs:/build:/style:
Step 4: Compare with Existing Fragments
Read every fragment in changelog/unreleased/. A commit is covered when a fragment's covers: frontmatter names it (by subject or SHA); a fragment with no declaration falls back to a fuzzy match on key terms. Only propose genuinely missing entries.
Fragments written by --apply declare covers: for the commit they cover, so rewriting their prose for a human never un-covers the commit.
Step 5: Present Proposals
Show proposed entries grouped by category:
## Proposed Changelog Fragments
**Tag**: [tag]
**Commits analyzed**: [count]
**Already covered**: [count]
**New entries proposed**: [count]
### Added
- [user-friendly description] ([sha])
### Changed
- [user-friendly description] ([sha])
### Fixed
- [user-friendly description] ([sha])
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.
- 3d ago First seen · 109 lines · 11 tokens per session scan A a1664df292c3
backfill is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 843 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-08-31.
Other commands, from other repositories
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
swarm-planner
Generates a structured execution plan with dependency tracking using the Swarms-inspired planning methodology.
review-queue
Display and manage the human review queue for parallel autonomous operations.
taskrunner-add
Add a task to the autonomous queue.
ocean-stop
Gracefully stop the boil-ocean run and its scheduler.
code-review
Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts looks good - must find minimum issues and can auto-fix with user approval.