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/jenova-marie/iris-mcp/git-commitgit clone --depth 1 https://github.com/jenova-marie/iris-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.02394 |
| Opus 5 | $0.00000 | $0.01197 |
| Sonnet 5 | $0.00000 | $0.00479 |
| Haiku 4.5 | $0.00000 | $0.00239 |
Grade A, and why
git-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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Command for Codex7
Create well-organized, properly attributed git commits for the Codex7 project.
Instructions
You are helping create git commits for the Codex7 monorepo. Follow these guidelines:
Commit Organization
-
Group related changes logically - Don't commit everything at once
- Documentation changes together
- Infrastructure/config changes together
- Feature implementation by package
- Tests with the code they test
- Bug fixes isolated from features
-
Commit frequently - Smaller, focused commits are better than large ones
- Each commit should represent one logical change
- Commits should be atomic (can be reverted independently)
- Prefer multiple small commits over one large commit
Commit Message Format
Use conventional commit format with emojis:
<emoji> <type>(<scope>): <subject>
<body>
<footer>
Emoji Prefixes
- ✨
feat:- New features - 🐛
fix:- Bug fixes - 📝
docs:- Documentation only - 🎨
style:- Code style/formatting (no logic change) - ♻️
refactor:- Code refactoring - 🧪
test:- Adding or updating tests - 🔥
perf:- Performance improvements - 🏗️
chore:- Build process, tooling, dependencies - 🔒
security:- Security improvements - 🐳
docker:- Docker-related changes - 📦
deps:- Dependency updates - 🚀
deploy:- Deployment configuration - 🔧
config:- Configuration changes
Scopes (optional but encouraged)
shared- @codex7/shared packagemcp-server- @codex7/mcp-server packageapi- @codex7/api packageweb- @codex7/web packageindexer- @codex7/indexer packagestorage-postgres- @codex7/storage-postgres packagestorage-sqlite- @codex7/storage-sqlite packagestorage-qdrant- @codex7/storage-qdrant packagemonorepo- Root-level monorepo changesci- CI/CD workflowsdocker- Docker configurations
Subject Line
- Use imperative mood ("add" not "added" or "adds")
- Don't capitalize first letter after type
- No period at the end
- Keep under 72 characters
- Be descriptive but concise
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 · 334 lines · 0 tokens per session scan A 5966aa1ca0a6
git-commit is a command published in the GitHub repository jenova-marie/iris-mcp (1 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,394 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.
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.