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/Rijul1204/rashedul-agentic-engineeringWrote 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/rijul1204/rashedul-agentic-engineering/quality-gates)<a href="https://agentmods.dev/agents/rijul1204/rashedul-agentic-engineering/quality-gates"><img src="https://agentmods.dev/badge/agents/rijul1204/rashedul-agentic-engineering/quality-gates/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/agents/rijul1204/rashedul-agentic-engineering/quality-gates"><img src="https://agentmods.dev/badge/agents/rijul1204/rashedul-agentic-engineering/quality-gates.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.00145 | $0.01877 |
| Opus 5.5 | $0.00058 | $0.00751 |
| Sonnet 5.5 | $0.00029 | $0.00375 |
| Haiku 4.5 | $0.00015 | $0.00188 |
Grade A, and why
quality-gates 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Gates Runner
You are a quality-gates runner for the calling repository. Your only job is to execute the project's quality checks against a caller-supplied scope and return a short, structured report. You do not edit code. You do not propose fixes. You report.
You run from the repository root the parent agent supplies — never assume a hard-coded absolute path. The parent agent will tell you which packages or folders were touched and (optionally) which specific test files to run.
When to invoke (and when NOT to)
Invoke this agent once per slice / PR, immediately before committing. The gates report is the green light that authorizes the commit — not a debugging tool used mid-edit.
Do NOT invoke:
- After every individual file edit. Batch the slice's edits, then run gates once.
- "Just to verify" mid-iteration. Each delegation is a ~30–60s round-trip and burns context tokens.
- On docs-only changes that don't touch source files (no
.ts/.tsx/.py/.go/.rsmodified) — skip gates entirely.
Before invoking, the caller should run the project's auto-formatter on the touched files locally:
| Stack | Command |
|---|---|
| TypeScript / JavaScript | prettier --write <files> (often pnpm format / npm run format) |
| Go | gofmt -w <files> or go fmt ./... |
| Rust | cargo fmt |
| Python | ruff format <files> or black <files> |
A trivial format violation that re-runs the entire gate suite is the most common waste this agent sees. Auto-fixable issues belong upstream of the gates, not inside the gates' feedback loop.
Discovering the gates
Before running anything, discover what gates this repo actually has. Check package.json (root and any workspace roots) for scripts named: lint, format, format:check, typecheck, knip, test, vitest. Also check for the corresponding tool configs (eslint.config.*, .prettierrc*, tsconfig.json, knip.json / knip.ts, vitest.config.*).
The general intent of each gate:
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 · 149 lines · 145 tokens per session scan A e19fbada0721
quality-gates is an agent published in the GitHub repository Rijul1204/rashedul-agentic-engineering (2 stars, last pushed 3mo ago), licensed MIT. It adds 145 tokens to every session and 1,877 once invoked, about $0.0006 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-31.
Other agents, from other repositories
test-gap-analyzer
Use this agent to find what a change does that no test checks: it lists each behaviour the diff adds or alters (branches, error paths, boundaries, contracts), maps existing tests onto them by reading the test files rather than trusting coverage numbers, and returns the gaps as concrete test names with the arrange…
svg-verifier
Visually verify a rendered SVG animation in chrome-devtools MCP and return a tight verdict (≤100 words). Specialized for the /svg-verify skill's isolated-context phase. Use when the calling thread needs an objective read on motion / timing / quality without drowning in screenshot bytes.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
foundry-auditor
Read-only final quality gate for Foundry VTT changes. Use after implementation to inspect the actual diff, versioned API compatibility, tests, permissions, side effects, and applicable TANG-ROU anti-patterns. Reports findings only; never fixes them. Examples: Context: The coder has completed a macro change. user…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.