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/lf-decentralized-trust-labs/gitmesh/releasegit clone --depth 1 https://github.com/LF-Decentralized-Trust-labs/gitmeshWrote 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/commands/lf-decentralized-trust-labs/gitmesh/release)<a href="https://agentmods.dev/commands/lf-decentralized-trust-labs/gitmesh/release"><img src="https://agentmods.dev/badge/commands/lf-decentralized-trust-labs/gitmesh/release.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 | $0.00000 | $0.00004 |
| Opus 5 | $0.00000 | $0.00002 |
| Sonnet 5 | $0.00000 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
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 4d 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
Release command
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.
- 4d ago First seen · 2 lines · 0 tokens per session scan A e8d652956c40
release is a command published in the GitHub repository LF-Decentralized-Trust-labs/gitmesh (145 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4 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-30.
Other commands, from other repositories
loci-sync
Sync information between this project and the Loci brain index. Keep full project memory in the project repo.
release-note-csoar
Automates the creation of Cloud SOAR (Automation Service) release notes for platform updates, integration changes, and bug fixes.
doc
Use this command to create a new feature doc, how-to, concept, reference, or troubleshooting guide — it scaffolds the file, frontmatter, structure, and sidebar entry.
loci-scan
Refresh the current project's local Loci memory.
claude-tracker
List and browse your saved Claude Code sessions with status (running/inactive/VS Code).
oss
Daily OSS contribution check - uses CLI with --json for structured data.