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 skills add moabualruz/fulcrum --skill git-cliffgit clone --depth 1 https://github.com/moabualruz/fulcrumWrote 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/skills/moabualruz/fulcrum/git-cliff)<a href="https://agentmods.dev/skills/moabualruz/fulcrum/git-cliff"><img src="https://agentmods.dev/badge/skills/moabualruz/fulcrum/git-cliff.svg" alt="Measured on agentmods" 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.00047 | $0.00197 |
| Opus 5 | $0.00023 | $0.00098 |
| Sonnet 5 | $0.00009 | $0.00039 |
| Haiku 4.5 | $0.00005 | $0.00020 |
Grade A, and why
git-cliff 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 8d 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.
This is a copy
83% identical to bat — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
git-cliff
When to use
See references/when-to-use.md. Load only when this section is needed.
Invocation
See references/invocation.md. Load only when this section is needed.
Patterns
See references/patterns.md. Load only when this section is needed.
Anti-patterns
See references/anti-patterns.md. Load only when this section is needed.
Cross-refs
See references/cross-refs.md. Load only when this section is needed.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 28 lines · 47 tokens per session scan A cfa8f59c5efd
git-cliff is a skill published in the GitHub repository moabualruz/fulcrum (3 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 197 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to bat, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
prime-silo-devops
DevOps, SDLC, Tagging, and Release management instructions for Prime-Silo. Use this when asked to tag a new release, check CI/CD build status, or manage the SDLC.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
aiwg-pr
AIWG-specific pull request delivery workflow for AIWG product/workspace changes; not the generic repository PR process.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
git-mirror-audit
Verify configured secondary git mirrors are present and not drifting from the primary remote/default branch.
bump-sdk-version
Bump the FutureSearch SDK version across all files. Use when releasing a new SDK version, updating version numbers, or the user says bump version, release, version bump.