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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/quality-gate)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/quality-gate"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/quality-gate/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/commands/boparaiamrit/skills-by-amrit/quality-gate"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/quality-gate.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.00027 | $0.01306 |
| Opus 5 | $0.00014 | $0.00653 |
| Sonnet 5 | $0.00005 | $0.00261 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
quality-gate 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 12d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/quality-gate — Technical Quality Gate
Run a structured quality pipeline before commits or PRs. Auto-detects project type and runs appropriate checks.
Modes
| Mode | Steps | When to Use |
|---|---|---|
quick |
Build + Test | Fast sanity check during development |
full |
All 6 steps | Thorough check before important milestones |
pre-commit |
Build + Lint + Test | Before committing changes |
pre-pr |
All 6 + Coverage | Before opening a pull request |
Instructions
Step 1: Determine Mode
From $ARGUMENTS:
- If mode given: Use that mode
- If empty: Default to
full
Step 2: Auto-Detect Project Type
# Detect project type from manifest files
ls package.json pyproject.toml setup.py Cargo.toml go.mod pom.xml build.gradle Makefile 2>/dev/null
Determine:
- Node.js —
package.jsonexists - Python —
pyproject.tomlorsetup.pyexists - Rust —
Cargo.tomlexists - Go —
go.modexists - Java (Maven) —
pom.xmlexists - Java (Gradle) —
build.gradleexists
Read the manifest to detect available scripts/commands:
# For Node.js
cat package.json | grep -A 20 '"scripts"'
Step 3: Run Pipeline
Run the applicable steps based on mode:
Step 3a: Build Check (all modes)
# Node.js
npm run build 2>&1
# Python
python -m py_compile [main_module] 2>&1
# Rust
cargo build 2>&1
# Go
go build ./... 2>&1
Record: PASS/FAIL, duration, error count.
Step 3b: Type Check (full, pre-pr)
# Node.js (TypeScript)
npx tsc --noEmit 2>&1
# Python (mypy)
mypy . 2>&1
# Rust (included in build)
# Go (included in build)
Record: PASS/FAIL, error count.
Step 3c: Lint Check (full, pre-commit, pre-pr)
# Node.js
npm run lint 2>&1
# Python
ruff check . 2>&1 || flake8 . 2>&1
# Rust
cargo clippy 2>&1
# Go
golangci-lint run 2>&1
Record: PASS/FAIL, warning count, error count.
Step 3d: Test Suite (all modes)
# Node.js
npm test 2>&1
# Python
pytest 2>&1
# Rust
cargo test 2>&1
# Go
go test ./... 2>&1
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.
- 12d ago First seen · 211 lines · 27 tokens per session scan A aa2a5b514888
quality-gate is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 1,306 once invoked, about $0.0001 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-31.
Other commands, from other repositories
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
red-team
Stress-test a plan, strategy, PRD, or launch with a room of hostile expert personas before you commit.
CLAUDE
When debugging TUI commands like wt switch (interactive picker), use the tmux-cli skill (preferred) or MCP's node-terminal tools to test interactively.
release-check
Run the release-readiness umbrella + draft a tweet-length announcement.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.