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/titanzero/outlook-mcpWrote 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/rules/titanzero/outlook-mcp/git-commit)<a href="https://agentmods.dev/rules/titanzero/outlook-mcp/git-commit"><img src="https://agentmods.dev/badge/rules/titanzero/outlook-mcp/git-commit/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/rules/titanzero/outlook-mcp/git-commit"><img src="https://agentmods.dev/badge/rules/titanzero/outlook-mcp/git-commit.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.00692 | $0.00692 |
| Opus 5.5 | $0.00277 | $0.00277 |
| Sonnet 5.5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
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 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Messages
Follow the Conventional Commits standard.
Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
- type (required):
feat,fix,refactor,chore,docs,test,style,perf,ci,build - scope (optional): module affected —
auth,email,calendar,folder,rules,config,utils - description: imperative mood, English, lowercase, no trailing period, max ~72 characters
Structural Elements
- fix: patches a bug (correlates with PATCH in Semantic Versioning)
- feat: introduces a new feature (correlates with MINOR in Semantic Versioning)
- BREAKING CHANGE: a footer
BREAKING CHANGE:, or a!after the type/scope, introduces a breaking API change (correlates with MAJOR in Semantic Versioning); can be part of any type - Other types (
build,chore,ci,docs,style,refactor,perf,test) are allowed and have no implicit SemVer effect unless they include a BREAKING CHANGE - Footers other than
BREAKING CHANGE: <description>may be provided and follow git trailer format
Specification Rules
- Commits MUST be prefixed with a type, followed by OPTIONAL scope, OPTIONAL
!, and REQUIRED terminal colon and space featMUST be used when a commit adds a new feature;fixMUST be used for bug fixes- A scope MAY be provided after the type, surrounded by parenthesis, e.g.
fix(parser): - A description MUST immediately follow the colon and space — short summary of code changes
- A longer body MAY follow the description, separated by one blank line; free-form, any number of paragraphs
- One or more footers MAY be provided one blank line after the body; each footer uses a word token followed by
:<space>or<space>#separator - Footer tokens MUST use
-in place of whitespace (exception:BREAKING CHANGE) - Breaking changes MUST be indicated in the type/scope prefix (
!) or as aBREAKING CHANGE:footer - Types are NOT case sensitive, except
BREAKING CHANGEwhich MUST be uppercase BREAKING-CHANGEis synonymous withBREAKING CHANGEwhen used as a footer token
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 · 62 lines · 692 tokens per session scan A 7cd707b8300a
git-commit is a cursor rule published in the GitHub repository titanzero/outlook-mcp (1 stars, last pushed 4mo ago), licensed MIT. It adds 692 tokens to every session, about $0.0028 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other cursor rules, from other repositories
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.