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 harness/harness-ai --skill approve-exemptgit clone --depth 1 https://github.com/harness/harness-aiWrote 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/harness/harness-ai/approve-exempt)<a href="https://agentmods.dev/skills/harness/harness-ai/approve-exempt"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/approve-exempt/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/harness/harness-ai/approve-exempt"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/approve-exempt.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.00168 | $0.05951 |
| Opus 5 | $0.00084 | $0.02975 |
| Sonnet 5 | $0.00034 | $0.01190 |
| Haiku 4.5 | $0.00017 | $0.00595 |
Grade A, and why
approve-exempt 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 9d 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.
This is a copy
100% identical to approve-exempt — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Approve Exemption
Approve one or more Pending STO security exemptions. This skill covers the approval
workflow after someone has requested an exemption (see /exempt-vuln for creation).
Pending scope is only PROJECT, PIPELINE, or TARGET. Exemptions are requested at
project, pipeline, or target scope only (All Issues → project; Vulnerabilities tab → project,
pipeline, or target). STO does not create pending requests at org or account scope — those
wider scopes exist only after elevation on approve (body.scope ORG or ACCOUNT). You
will not see scope: ORG or scope: ACCOUNT on rows from status: Pending in normal flows.
If a list row shows ORG/ACCOUNT, it is already approved/widened (re-approve or a different
workflow), not a fresh pending request this skill targets.
Harness exposes two different "scope" ideas — do not mix them up:
| Concept | What it controls | How you use it |
|---|---|---|
| Listing scope | Which project's exemption queue you read | Always list at project scope. Never pass resource_scope='account' or 'org' to harness_list. |
| Approval scope | Where the exemption becomes effective after approval | Passed as body.scope on harness_execute — CURRENT, PROJECT, ORG, or ACCOUNT. |
Users almost always say approve, even when they want org- or account-wide coverage. Treat
"approve for org", "org-wide", and "at account level" as approve with elevation — the MCP
server routes those to the promote endpoint internally. You never need a separate
action='promote' call; always use action='approve' with the right body.scope.
Keep the Harness UI out of the loop. Do not ask the user to copy issue titles, CVEs, or
exemption IDs from the platform. Your default opening move is to list pending exemptions in
chat, show a numbered table, report total, and let them pick by row number (or narrow with
search if they volunteer a keyword). Pagination surfaces more rows on request — you never dump
the full queue at once.
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.
- 9d ago First seen · 432 lines · 168 tokens per session scan A 3ad2b844f6c6
approve-exempt is a skill published in the GitHub repository harness/harness-ai (19 stars, last pushed 18d ago), licensed Apache-2.0. It adds 168 tokens to every session and 5,951 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to approve-exempt, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…