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/ankushdixit/claude-pluginsWrote 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/ankushdixit/claude-plugins/end)<a href="https://agentmods.dev/commands/ankushdixit/claude-plugins/end"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/end/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/ankushdixit/claude-plugins/end"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/end.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.00010 | $0.01171 |
| Opus 5.5 | $0.00004 | $0.00468 |
| Sonnet 5.5 | $0.00002 | $0.00234 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade A, and why
end 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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session End
Complete the current development session by following these steps in order.
Step 1: Pre-flight Checks
Before completing the session, ensure all work is properly prepared.
1.1 Check CHANGELOG
First, check if CHANGELOG.md was updated in this session:
git diff --name-only main...HEAD | grep -q CHANGELOG.md && echo "CHANGELOG updated" || echo "CHANGELOG needs update"
If CHANGELOG needs update:
- Review commits made this session with
git log --oneline -10 - Update CHANGELOG.md under the
## [Unreleased]section with:- Features added under
### Added - Bug fixes under
### Fixed - Changes under
### Changed
- Features added under
- Stage the CHANGELOG:
git add CHANGELOG.md
1.2 Check and Commit Uncommitted Changes
Check for uncommitted changes:
git status --porcelain
If there are uncommitted changes:
- Review the changes
- Stage all changes:
git add -A - Create a commit with this format:
git commit -m "$(cat <<'EOF'
<type>: <short description>
<detailed description of changes>
LEARNING: <one key insight from this work>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
EOF
)"
Where <type> is one of: feat, fix, refactor, docs, test, chore
1.3 Generate Learnings
Extract 2-5 key learnings from the session and write them to a file:
cat > .session/temp_learnings.txt << 'EOF'
<learning 1 - technical insight or pattern discovered>
<learning 2 - gotcha or edge case encountered>
<learning 3 - best practice that worked well>
EOF
What makes a good learning:
- Technical insights discovered during implementation
- Gotchas or edge cases encountered
- Best practices or patterns that worked well
- Architecture decisions and their rationale
- Performance or security considerations
Step 2: Ask About Work Item Completion
Ask the user about the work item completion status using AskUserQuestion:
Question: Work Item Completion Status
- Question: "Is this work item complete? [Include work item title]"
- Header: "Completion"
- Multi-select: false
- Options:
- Label: "Yes - Mark as completed", Description: "Work item is done. A PR will be created for review."
- Label: "No - Keep as in-progress", Description: "Work is ongoing. Will auto-resume when you run /start."
- Label: "Cancel", Description: "Don't end session. Continue working."
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 · 175 lines · 10 tokens per session scan A 6a795e071e2c
end is a command published in the GitHub repository ankushdixit/claude-plugins (3 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 1,171 once invoked, about $0.0000 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
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
codex-review
Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.