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 cnkang/nginx-markdown-for-agents --skill nginx-markdown-harness-maintenancegit clone --depth 1 https://github.com/cnkang/nginx-markdown-for-agentsWrote 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/cnkang/nginx-markdown-for-agents/nginx-markdown-harness-maintenance)<a href="https://agentmods.dev/skills/cnkang/nginx-markdown-for-agents/nginx-markdown-harness-maintenance"><img src="https://agentmods.dev/badge/skills/cnkang/nginx-markdown-for-agents/nginx-markdown-harness-maintenance/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/cnkang/nginx-markdown-for-agents/nginx-markdown-harness-maintenance"><img src="https://agentmods.dev/badge/skills/cnkang/nginx-markdown-for-agents/nginx-markdown-harness-maintenance.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.00064 | $0.01179 |
| Opus 5.5 | $0.00026 | $0.00472 |
| Sonnet 5.5 | $0.00013 | $0.00236 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
nginx-markdown-harness-maintenance 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NGINX Markdown Harness Maintenance
Keep harness changes aligned with repo-owned truth surfaces and run the right verification matrix with minimal guesswork.
Quick Start
- Resolve current spec intent:
python3 tools/harness/resolve_spec.py --hint "<task summary>" - Route changed files to risk packs:
python3 skills/nginx-markdown-harness-maintenance/scripts/harness_route.py --from-git - Run cheap blockers first:
make harness-check - Run focused or umbrella checks from the route output.
- If docs/release wiring changed, run:
make harness-check-full
Example Output
$ python3 skills/nginx-markdown-harness-maintenance/scripts/harness_route.py --from-git
files: 2
- docs/harness/README.md
- docs/harness/HARNESS_MAINTENANCE.md
matched risk packs: 1
- docs-tooling-drift (docs/harness/risk-packs/docs-tooling-drift.md)
path hits:
- docs/harness/HARNESS_MAINTENANCE.md
- docs/harness/README.md
keyword hits:
- docs
verification families: 3
- [cheap-blocker] docs-tooling
- [cheap-blocker] harness-sync
- [umbrella] release-quality
Workflow
- Treat
AGENTS.mdanddocs/harness/as canonical contract surfaces. - Use
tools/harness/resolve_spec.pybefore broad edits. TriageWARN_NEEDS_AUTHOR_REVIEWagainst the user request and current evidence. Record a resolved warning and continue. Ask only when missing information materially affects correctness or authorized scope; pause only dependent work. Missing optional specs do not block an explicit task. - Use
python3 skills/nginx-markdown-harness-maintenance/scripts/harness_route.py --from-gitto map changed files/hints to risk packs and verification families fromdocs/harness/routing-manifest.json. - Build a phased matrix:
cheap-blockerfirst- then
focused-semantic - then
umbrellaonly when needed
- On first drift trigger:
- identify minimal changed files related to the failing family
- rerun only affected verification family commands
- run
make harness-checkbefore broad retries - if the same approach yields no new evidence or progress, change approach or escalate with relevant redacted error output and affected surfaces
- Keep optional local adapters optional. Missing local files must degrade as
SKIP_NOT_PRESENT, not repository failure. - If harness behavior changes, synchronize the affected truth surfaces and
consumers in the same change set. Inspect
AGENTS.md,docs/harness/,tools/harness/,Makefile, and CI; edit only consumers that need changes. - Follow explicit user scope over skill workflow defaults. Reviews and plans do not authorize writes. If this skill causes a pause, link this file, quote the applicable instruction, and explain the unresolved dependency.
- Finish after applicable checks pass. Repeat checks only for new edits, failures, or unresolved risks; retain required production-code gates.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +10 lines f0cb5516f719
- 2mo ago Changed fd91e130ac5e
- 2mo ago First seen · 89 lines · 64 tokens per session scan A 1aaf00ea8034
nginx-markdown-harness-maintenance is a skill published in the GitHub repository cnkang/nginx-markdown-for-agents (25 stars, last pushed 3d ago), licensed BSD-2-Clause. It adds 64 tokens to every session and 1,179 once invoked, about $0.0003 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.
nginx-markdown-harness-maintenance compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| nginx-markdown-harness-maintenancecnkang/nginx-markdown-for-agents | Skill | 25 | 3d ago | BSD-2-Clause | A | 64 | Codex |
| firecrawl-buildfirecrawl/firecrawl | Skill | 199k | yesterday | AGPL-3.0 | A | 149 | Claude Code, Codex |
| firecrawl-build-onboardingfirecrawl/firecrawl | Skill | 199k | yesterday | AGPL-3.0 | A | 89 | Claude Code, Codex |
| firecrawl-build-scrapefirecrawl/firecrawl | Skill | 199k | yesterday | AGPL-3.0 | A | 62 | Claude Code, Codex |
| firecrawl-build-searchfirecrawl/firecrawl | Skill | 199k | yesterday | AGPL-3.0 | A | 54 | Claude Code, Codex |
| firecrawl-build-interactfirecrawl/firecrawl | Skill | 199k | yesterday | AGPL-3.0 | A | 56 | Claude Code, Codex |
| autonomous-loopsaffaan-m/ECC | Skill | 298k | 4d ago | MIT | A | 26 | Claude Code, Kiro |