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/hint-services/obsidian-github-mcp/releasegit clone --depth 1 https://github.com/Hint-Services/obsidian-github-mcpWhat 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.00000 | $0.00764 |
| Opus 5 | $0.00000 | $0.00382 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
release 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 2d 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 are an AI engineer tasked with creating a new version release for the project. Your goal is to analyze recent changes, bump the version, update the changelog, create a git tag, and publish a GitHub release. Follow these steps carefully:
-
Analyze recent changes since the last version: <release_type> $ARGUMENTS </release_type>
-
Review the current version in package.json and recent commits to understand what type of release this should be (patch, minor, or major) based on semantic versioning principles.
-
Create a comprehensive release plan including: <release_plan> Current Version: [Current version from package.json] New Version: [Proposed new version] Release Type: [patch/minor/major] Key Changes: [List of major changes since last version] </release_plan>
-
For version bumping and release creation: a. Update the version number in package.json c. Update CHANGELOG.md with comprehensive release notes including:
- New features (### Added)
- Improvements (### Improved)
- Bug fixes (### Fixed)
- Breaking changes if applicable (### Breaking Changes)
Note: The changelog is user-facing and should focus on user benefits rather than technical implementation details. Write from the user's perspective, highlighting what they can do or experience differently. You may omit technical implementation details that don't directly impact the user experience. d. Commit all changes with a descriptive release commit message e. Create an annotated git tag for the version f. Push the commit and tags to the remote repository
-
Create a GitHub release: a. Use the git tag as the release version b. Generate comprehensive release notes from the changelog c. Include highlights of major features and improvements d. Use appropriate emoji and formatting for better readability e. Publish the release on GitHub
-
Verify the release: a. Confirm the version is updated in all relevant locations b. Verify the git tag was created and pushed successfully c. Check that the GitHub release is published and visible d. Ensure the changelog follows proper formatting and completeness
Your final output should include:
- The release plan with version analysis
- A summary of all files updated
- The commit message used
- The git tag created
- A link to the published GitHub release
Format your final output as follows: <release_output> <release_plan> [Your comprehensive release plan] </release_plan>
<files_updated> [List of files that were updated during the release process] </files_updated>
<version_changes> [Summary of version number changes made] </version_changes>
<commit_details> Commit Message: [The release commit message] Git Tag: [The git tag created] </commit_details>
<github_release> Release URL: [Link to the published GitHub release] Release Title: [The GitHub release title] </github_release>
<verification_checklist>
- package.json version updated
- CHANGELOG.md updated with comprehensive notes
- Release commit created and pushed
- Git tag created and pushed
- GitHub release published
- All changes verified and functional </verification_checklist> </release_output>
Remember to follow semantic versioning principles:
- Patch (x.x.X): Bug fixes and small improvements
- Minor (x.X.x): New features that don't break existing functionality
- Major (X.x.x): Breaking changes or major architectural updates
Wait for user confirmation before proceeding with each major step of the release process.
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.
- 2d ago First seen · 95 lines · 0 tokens per session scan A fdee0a6588cb
release is a command published in the GitHub repository Hint-Services/obsidian-github-mcp (9 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 764 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-31.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.