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 agentmods add skills/vanillagreencom/kendex/harness-cinpx skills add vanillagreencom/kendex --skill harness-cigit clone --depth 1 https://github.com/vanillagreencom/kendexWrote 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/vanillagreencom/kendex/harness-ci)<a href="https://agentmods.dev/skills/vanillagreencom/kendex/harness-ci"><img src="https://agentmods.dev/badge/skills/vanillagreencom/kendex/harness-ci.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.00019 | $0.00635 |
| Opus 5 | $0.00010 | $0.00318 |
| Sonnet 5 | $0.00004 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
harness-ci 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 yesterday.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness CI
Run the classifier to decide whether CI can skip product checks. Commit .kendex-generated.json with the renders after kendex refresh. The engine writes that inventory from rendered artifacts. In-place content and carrier package source remain outside it.
.agents/skills/harness-ci/scripts/harness-only \
--event pull_request --base "$BASE_SHA" --head "$HEAD_SHA"
Flags and exit codes: harness-only --help. Contract and semantics: README.md. Workflow shapes to copy: references/wiring.md.
This package never edits a workflow
Nothing here writes .github/. Wire the one step yourself, once, from references/wiring.md.
The rules to hold when wiring it
Classify inside a job, never in on.<event>.paths. A path filter stops the workflow from starting, the required context is never created, and a merge queue waits forever on a check nothing will report.
Keep the required-context job unconditional. Gate the expensive lanes with a job-level if: off a changes job's output, or a step-level if: inside an aggregate, and let the aggregate that carries the required name run on every event.
A job-level if: needs a status function. Without one it keeps the implicit success() and skips the lane whenever the classifying job failed, which stands the expensive lanes down on exactly the diffs nothing classified. An aggregate accepts a skipped lane only after checking that the classifier ran and cleared the diff.
A lane reading a path family beside the verdict needs more than the status function. A dead classifying job publishes no outputs, so the family term reads empty and skips the lane on its own. Lift it behind needs.changes.result != 'success', the two-gate shape in references/wiring.md.
Reading a verdict
stdout is the verdict line alone; changed paths and reasons go to stderr; exit 2 is a wiring error that prints no verdict. README.md § Semantics.
What ships with it
12 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.
- DEVELOPMENT.md 2.7 KB
- README.md 3.1 KB
- references/wiring.md 8.0 KB
- scripts/harness-only 7.9 KB
- tests/event-ranges.test.sh 2.8 KB runs code
- tests/fail-closed.test.sh 4.8 KB runs code
- tests/in-place.test.sh 777 B runs code
- tests/lib/sandbox.sh 2.8 KB runs code
- tests/path-set.test.sh 4.4 KB runs code
- tests/rename-into-render.test.sh 2.1 KB runs code
- tests/wiring-errors.test.sh 5.4 KB runs code
- tests/wiring-shapes.test.sh 5.0 KB runs code
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.
- yesterday Changed · -28 lines 9bc5313a9ab2
- 2d ago Changed · -22 lines 3e9f8b6c4377
- 6d ago First seen · 98 lines · 19 tokens per session scan A b4767e222f61
harness-ci is a skill published in the GitHub repository vanillagreencom/kendex (74 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 635 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-30.
Other skills, from other repositories
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
prose-review
Review prose written for others (e.g., user-facing documentation, prompts for other LLMs, reports, plans, inline comments, docstrings) for local jargon leakage, orphaned references, missing grounding, and audience or genre mismatch. Always run on prose you produce or materially edit, except for routine conversational…
text-search
Search indexed text corpora with qmd. For indexed content, prefer qmd over grep.
xcodebuildmcp
Build/test Xcode projects via the XcodeBuildMCP MCP server using a local CLI wrapper for pi (no MCP support). Use when the user mentions Xcode, xcodebuild, iOS builds/tests, or XcodeBuildMCP.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
deep-x-research
Deep, exhaustive research on a topic across X (Twitter) by driving Grok (x.com/i/grok) through surf. Use when the user wants comprehensive X research on a concept, technique, trend, tool, or creator scene; needs categorized findings with every claim traceable to post URLs; or when a single Grok query is not enough.