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/danielsimonjr/memory-mcp/commitgit clone --depth 1 https://github.com/danielsimonjr/memory-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.00021 | $0.01026 |
| Opus 5 | $0.00010 | $0.00513 |
| Sonnet 5 | $0.00004 | $0.00205 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
COMMIT 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 yesterday.
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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Commit Workflow
Execute a complete commit workflow with quality checks and version management.
Arguments
-
Version Type (required):
major,minor, orpatchmajor- Breaking changes, major features (1.0.0 → 2.0.0)minor- New features, enhancements (1.0.0 → 1.1.0)patch- Bug fixes, cleanup, debug (1.0.0 → 1.0.1)
-
Description (required): Brief description of changes for changelog
Workflow Steps
Execute these steps in order. Stop immediately if any step fails.
Step 1: Pre-flight Checks
cd C:/mcp-servers/memory-mcp && git status
Verify:
- Working directory is clean or has only expected changes
- On correct branch (usually
main)
Step 2: TypeScript Type Check
cd C:/mcp-servers/memory-mcp && npm run typecheck
STOP if typecheck fails. Fix type errors before continuing.
Step 3: Run Tests
cd C:/mcp-servers/memory-mcp && npm test
STOP if tests fail. Fix failing tests before continuing.
Step 4: Version Bump
Read current version from package.json, then increment based on version type:
| Type | Example |
|---|---|
| major | 9.2.1 → 10.0.0 |
| minor | 9.2.1 → 9.3.0 |
| patch | 9.2.1 → 9.2.2 |
Update package.json with new version.
Step 5: Update CHANGELOG.md
Add new section at top of changelog (after header):
## [X.Y.Z] - YYYY-MM-DD
### Added/Changed/Fixed
- **Category**: Description of changes
- Detail 1
- Detail 2
Use appropriate section header:
### Added- New features### Changed- Changes to existing features### Fixed- Bug fixes### Removed- Removed features
Step 6: Update CLAUDE.md
Update test count if tests were added:
npm test # Run tests with coverage (XXXX tests)
Update version reference if present.
Step 7: Git Commit
cd C:/mcp-servers/memory-mcp && git add -A && git commit -m "$(cat <<'EOF'
<type>: v<version> - <description>
<detailed bullet points of changes>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <[email protected]>
EOF
)"
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.
- yesterday First seen · 167 lines · 21 tokens per session scan A 2f04205ad35e
COMMIT is a command published in the GitHub repository danielsimonjr/memory-mcp (3 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 1,026 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.