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 TheArchitectit/agent-guardrails-template --skill commit-validatorgit clone --depth 1 https://github.com/TheArchitectit/agent-guardrails-templateWrote 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/thearchitectit/agent-guardrails-template/commit-validator)<a href="https://agentmods.dev/skills/thearchitectit/agent-guardrails-template/commit-validator"><img src="https://agentmods.dev/badge/skills/thearchitectit/agent-guardrails-template/commit-validator/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/skills/thearchitectit/agent-guardrails-template/commit-validator"><img src="https://agentmods.dev/badge/skills/thearchitectit/agent-guardrails-template/commit-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 23 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00023 | $0.00302 |
| Opus 5.5 | $0.00009 | $0.00121 |
| Sonnet 5.5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
commit-validator 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.
What it actually says
Commit Validator Agent
Validate all git commits against COMMIT_WORKFLOW.md standards.
Validation Rules
1. AI Attribution (REQUIRED)
Every commit message MUST include AI attribution: Co-Authored-By: Claude <[email protected]>
2. Single Focus Rule
- One commit = One logical change
- No unrelated changes in the same commit
3. No Secrets in Diff
Scan for API keys, tokens, passwords, private keys, .env contents, DB connection strings. Block immediately if found.
4. Pre-Commit Requirements
- All relevant tests MUST pass
- No linting or formatting errors
- Code has been self-reviewed
Commit Message Format
<type>: <description>
[optional body]
Co-Authored-By: Claude <[email protected]>
Types: feat, fix, docs, style, refactor, test, chore
Validation Failure Actions
If validation fails:
- Block the commit
- Explain the violation
- Provide specific fix instructions
- Require user confirmation before proceeding
References
docs/workflows/COMMIT_WORKFLOW.md- Commit standardsskills/shared-prompts/error-recovery.md- Recovery procedures
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 · 55 lines · 23 tokens per session scan A 0c51b72a291d
commit-validator is a skill published in the GitHub repository TheArchitectit/agent-guardrails-template (1 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 23 tokens to every session and 302 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
code-changes
Change the user's own program, on their machine or through GitHub. Use when a request needs a change to the user's code (instrument tracing, wire the SDK, fix the agent behind a failing scenario, add a run parameter to a connected agent, version a hardcoded prompt) and not when the platform alone can do it (create a…
git-expert
Expert-level Git version control with advanced workflows, branching strategies, and best practices for team collaboration. Use when the user mentions version control, collaboration, or workflow, or when the task involves Essential Git Commands, Advanced Git Techniques, Branching Strategies, or Conflict Resolution.
tldr-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /tldr-commit.…
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.