Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jrjsmrtn/project-orchestration-skillsnpx agentmods add skills/jrjsmrtn/project-orchestration-skills/validate-quality-configWrote 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/jrjsmrtn/project-orchestration-skills/validate-quality-config)<a href="https://agentmods.dev/skills/jrjsmrtn/project-orchestration-skills/validate-quality-config"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/validate-quality-config/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/jrjsmrtn/project-orchestration-skills/validate-quality-config"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/validate-quality-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.04049 |
| Opus 5 | $0.00019 | $0.02024 |
| Sonnet 5 | $0.00008 | $0.00810 |
| Haiku 4.5 | $0.00004 | $0.00405 |
Grade A, and why
validate-quality-config 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 11d 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Quality Configuration
Validate consistency across quality configuration files.
When to Use
- After running
setup-git-hooksskill - When debugging "works locally, fails in CI" issues
- Before major releases or audits
- When onboarding to understand quality setup
- After updating any quality-related configuration
What It Validates
The consistency chain:
docs/reference/quality-configuration.md ← Single source of truth
↓ must match
.editorconfig ← Editor formatting
↓ must match
Linter configs ← Code analysis
↓ must match
.pre-commit-config.yaml ← Local hooks
↓ must match
.github/workflows/*.yml ← CI pipeline
.gitlab-ci.yml
Plus one axis that is not a match but a required difference:
Language manifest → toolchain FLOOR (go.mod, Cargo.toml, pyproject.toml, package.json, mix.exs)
CI config → toolchain BUILD (go-version:, python-version:, node-version:, matrix)
these must NOT be the same value
Also validated: that the toolchain floor (language manifest) and build version (CI) are deliberately different, and that only the floor-compatibility job reads the manifest. This is the one assertion in this skill that checks a difference rather than a match.
Required Inputs
- A project that already has quality configuration in place (run
setup-git-hooksfirst) docs/reference/quality-configuration.mdas the single source of truth for canonical values- Read access to the config files being cross-checked (
.editorconfig, linter configs such as.credo.exs/ruff.toml/.prettierrc,.pre-commit-config.yaml, and the CI workflow files under.github/workflows/or.gitlab-ci.yml)
Workflow
Step 1: Check Reference Document Exists
# Verify single source of truth exists
if [ -f docs/reference/quality-configuration.md ]; then
echo "✓ quality-configuration.md exists"
else
echo "✗ Missing docs/reference/quality-configuration.md"
echo " Run: quality/setup-git-hooks skill first"
exit 1
fi
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.
- 11d ago First seen · 396 lines · 38 tokens per session scan A 00c9b2a18b69
validate-quality-config is a skill published in the GitHub repository jrjsmrtn/project-orchestration-skills (15 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 4,049 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 skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
test-setup
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.