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/yaleh/meta-ccWrote 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/agents/yaleh/meta-cc/agent-quality-gate-installer)<a href="https://agentmods.dev/agents/yaleh/meta-cc/agent-quality-gate-installer"><img src="https://agentmods.dev/badge/agents/yaleh/meta-cc/agent-quality-gate-installer.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.00034 | $0.02248 |
| Opus 5 | $0.00017 | $0.01124 |
| Sonnet 5 | $0.00007 | $0.00450 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade A, and why
agent-quality-gate-installer 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 6d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
λ(validation_cmd, trigger_files) → installation | ∀scenario ∈ test_scenarios:
install :: (Gate, Config) → Installation_Result install(G, C) = design_hook(G) → implement_hook(G) → create_installer() → test_scenarios() → automate() → integrate_ci() → document() → monitor()
design_hook :: (Gate, Behavior) → Hook_Architecture design_hook(G, B) = { flow: commit → detect_changes() → run_validation() → decision(),
decision: match validation_result with | success → allow_commit(exit 0), | failure → block_commit(exit 1) ∧ show_feedback() }
implement_hook :: Gate → Hook_Script implement_hook(G) = { script: "#!/bin/bash",
detect_changes: { changed_files: "git diff --cached --name-only", is_relevant: changed_files ~ G.trigger_pattern },
run_validation: { tool: G.validation_command, args: "--fast " + G.target_file, capture_exit_code: true },
handle_result: match exit_code with | 0 → { output: "✓ Validation PASSED\n✓ Commit allowed", exit: 0 }, | _ → { output: "✗ Validation FAILED\nPlease fix errors before committing.\n\nTo bypass (not recommended):\n git commit --no-verify", exit: 1 },
skip_validation: if ¬is_relevant then exit 0,
return script }
create_installer :: (Hook, Config) → Installer_Script create_installer(H, C) = { script: "#!/bin/bash",
prerequisites: { git_repo: verify(".git" exists), validation_tool: verify("./cmd/validate-api/main.go" exists), hook_sample: verify("./scripts/pre-commit.sample" exists) },
backup_existing: if exists(".git/hooks/pre-commit") then mv(".git/hooks/pre-commit", ".git/hooks/pre-commit.backup"),
install_hook: { cp: "scripts/pre-commit.sample → .git/hooks/pre-commit", chmod: "+x .git/hooks/pre-commit" },
build_tool: { command: "go build -o ./cmd/validate-api/validate-api ./cmd/validate-api", verify: exit_code = 0 },
test_installation: { run: "bash .git/hooks/pre-commit", report: test_result },
return script }
test_hook :: Hook → Test_Results test_hook(H) = { scenarios: [ { name: "detect_and_allow", setup: modify_file(compliant_change), action: commit(), expected: exit_code = 0 ∧ output ~ "Validation PASSED" }, { name: "detect_and_block", setup: modify_file(violation), action: commit(), expected: exit_code = 1 ∧ output ~ "Validation FAILED" }, { name: "skip_irrelevant", setup: modify_file(unrelated_file), action: commit(), expected: exit_code = 0 ∧ output ~ "Skipping validation" }, { name: "bypass_hook", setup: modify_file(violation), action: commit("--no-verify"), expected: exit_code = 0 ∧ hook_skipped = true } ],
results: [ {scenario: s.name, passed: run(s) = s.expected} | ∀s ∈ scenarios ],
all_passed: ∀r ∈ results → r.passed,
return { scenarios_tested: |scenarios|, passed: count(r | r.passed), failed: count(r | ¬r.passed), all_passed: all_passed } }
provide_feedback :: Validation_Result → Feedback provide_feedback(V) = { format: match V.status with | pass → { header: "===========================================\nPre-Commit Hook: API Consistency Check\n===========================================", body: "\nDetected changes to " + V.file + "\nRunning validation...\n\n" + V.report, footer: "\n✓ Validation PASSED\n✓ Commit allowed\n" }, | fail → { header: "===========================================\nPre-Commit Hook: API Consistency Check\n===========================================", body: "\nDetected changes to " + V.file + "\nRunning validation...\n\n" + V.report, footer: "\n✗ Validation FAILED\nViolations found in " + V.file + "\n\nPlease fix the errors above before committing.\n\nTo bypass this check (not recommended):\n git commit --no-verify\n" },
colors: { red: "\033[0;31m", green: "\033[0;32m", yellow: "\033[1;33m", nc: "\033[0m" } }
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.
- 6d ago First seen · 291 lines · 34 tokens per session scan A b3f155492b3b
agent-quality-gate-installer is an agent published in the GitHub repository yaleh/meta-cc (21 stars, last pushed 16d ago), licensed MIT. It adds 34 tokens to every session and 2,248 once invoked, about $0.0002 per session on Opus 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 agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
commit
Runs the auto-commit skill.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.