complete

complete is a command for Claude Code from ruvnet/ruv-FANN. It costs 0 tokens per session (532 once invoked), scanned A, original, MIT.

A command for marking a GitHub issue as completed by the agent team. It can post a completion comment, link a pull request, remove the team’s claim label, and optionally close the issue.

In plain words
What is it for?
Use it to complete an issue, attach the pull request containing the changes, add a custom message, or close the issue.
Why use it?
It keeps issue status and team coordination records up to date after work has finished.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/ruvnet/ruv-fann/complete
Clone the repo
git clone --depth 1 https://github.com/ruvnet/ruv-FANN

Made for: Claude Code.

Wrote 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.

agentmods badge for complete

README.md
[![agentmods](https://agentmods.dev/badge/commands/ruvnet/ruv-fann/complete.svg)](https://agentmods.dev/commands/ruvnet/ruv-fann/complete)
Your own site
<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/complete"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/complete.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 532 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00532
Opus 5 $0.00000 $0.00266
Sonnet 5 $0.00000 $0.00106
Haiku 4.5 $0.00000 $0.00053

Measured 4d ago against content hash 9667f41116e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

complete 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.

.claude/commands/github/complete.md · 106 lines

What it actually says

/github complete

Marks a GitHub issue as completed by your swarm, optionally linking to the PR with changes.

Usage

/github complete <issue_number> [options]

Options

  • --pr <number> - Link to pull request with changes
  • --message <text> - Custom completion message
  • --close - Also close the issue (default: false)

Examples

/github complete 45
/github complete 45 --pr 123
/github complete 45 --pr 123 --close
/github complete 45 --message "Fixed with new caching strategy"

What it does

  1. Removes swarm-claimed label
  2. Posts completion comment with:
    • Summary of work done
    • Link to PR (if provided)
    • Any relevant notes
  3. Optionally closes the issue
  4. Updates coordination tracking

Implementation

Uses GitHub MCP to:

  1. Verify task ownership
  2. Remove claim label
  3. Post completion comment
  4. Optionally close issue
  5. Link to PR if provided

Example Interactions

Basic Completion

> /github complete 45

✅ Marked issue #45 as complete
Removed swarm claim
Posted completion notice

With PR Link

> /github complete 45 --pr 123

✅ Marked issue #45 as complete
Linked to PR #123
Posted: "Task completed in PR #123"

With Close

> /github complete 45 --pr 123 --close

✅ Marked issue #45 as complete
Linked to PR #123
Issue closed
Posted: "Task completed and verified in PR #123"

Completion Message Format

✅ Task Complete by swarm `<your-id>`

Changes implemented in PR #123

Summary:
- Fixed memory leaks in neural agent
- Added cleanup handlers
- Improved performance by 40%

All tests passing. Ready for review.

---
Completed at: <timestamp>

Best Practices

  1. Always link to your PR if you made changes
  2. Summarize what was actually done
  3. Only close if you're certain it's fully resolved
  4. Mention any follow-up work needed
  5. Thank collaborators if applicable
  • /github claim <number> - Initial task claim
  • /github update <number> - Progress updates
  • /github release <number> - Release without completing
  • /github my-tasks - View your tasks
Changes

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.

  1. 4d ago First seen · 106 lines · 0 tokens per session scan A 9667f41116e8

Subscribe to this mod's changes

complete is a command published in the GitHub repository ruvnet/ruv-FANN (378 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 532 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-30.