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 Cynrath/agent-context-kit --skill ackit-policy-authoringgit clone --depth 1 https://github.com/Cynrath/agent-context-kitWrote 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/cynrath/agent-context-kit/ackit-policy-authoring)<a href="https://agentmods.dev/skills/cynrath/agent-context-kit/ackit-policy-authoring"><img src="https://agentmods.dev/badge/skills/cynrath/agent-context-kit/ackit-policy-authoring/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/cynrath/agent-context-kit/ackit-policy-authoring"><img src="https://agentmods.dev/badge/skills/cynrath/agent-context-kit/ackit-policy-authoring.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.00023 | $0.00399 |
| Opus 5.5 | $0.00009 | $0.00160 |
| Sonnet 5.5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
ackit-policy-authoring 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.
What it actually says
Policy Authoring
Activate when the user asks to codify scan thresholds or team-wide rule overrides.
See merge order for precedence and digest.
Steps
- Start from
ackit.yml; add a policy layer withschemaVersion: 1andextends(local repo-relative files ornpm:<pkg>/<file>for already-installed packages only — resolution is offline by construction, remote fetch is refused withPOL-OFFLINE-BLOCKED). - Scope overrides with
org/repo/pathScopes; lock security-relevant rules withlocked: trueso downstream layers cannot weaken them (POL-LOCKED-CONFLICT; deny is sticky across layers). Suppressions requirereasonand supportexpiresAt. - Verify with
ackit policy check(chain plus digest plus autonomy plus review plus problems) andackit config check(schema validation). Risk tiers (tier0 allowthroughtier4 deny) enforce ONLY at ACKit-owned boundaries (task complete --force,checkpoint export,verification record): explicitdenyrefuses withPOLICY-TIER-DENIED(exit 4); explicitaskin a non-interactive context denies. Optionalreview:(requireddimensions plusblockingSeverity) gatesPASS-family verdicts viaVERDICT_BLOCKING.
Notes
- Remote URL auto-fetch is forbidden; dependencies must be pre-installed.
- Deterministic merge: defaults <
ackit.yml< policy extends chain (declaration order) < CLI flags; arrays replace, objects merge; digest is sha256 over sorted-key JSON. - Repositories without
autonomy:/review:see zero behavior change.
What ships with it
1 file 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 14af96adcbfe
- 1mo ago First seen · 24 lines · 23 tokens per session scan A 0381477aa92a
ackit-policy-authoring is a skill published in the GitHub repository Cynrath/agent-context-kit (14 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 399 once invoked, about $0.0001 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.
Other skills, from other repositories
steadyagent-workflow
Local-first Codex workflow for planning, debugging, reviewing, refactoring, improving AGENTS.md, building skills, publishing agent harness repositories, or running complex multi-step coding tasks that need staged diagnosis, context control, verification loops, review strategy, release evidence, and…
agents-doctor
Validate AGENTS.md and related agent instruction files with the published agents-doctor CLI. Use when the user asks to check, lint, verify, explain, audit, fix, release-check, or compare AGENTS.md, CLAUDE.md, GEMINI.md, agent instruction inheritance, tool profiles, context fidelity, instruction graphs, GitHub…
adding-an-audit-check
Add a new audit check to agent-context-doctor end to end, including config, suppressions, the check catalog, tests, and docs. Use when asked to detect a new kind of problem in agent instruction files.
repository-bootstrap
Audit and establish or upgrade the canonical repository governance baseline. Use only when explicitly asked to bootstrap, standardize, or upgrade a repository; do not use for feature development or source-code restructuring.
repository-hygiene
Perform a read-only evidence-based audit of stale docs, agent files, scripts, generated artifacts, duplicate code, and optional tools. Use only when explicitly asked for cleanup or governance review; do not delete or refactor during the audit.
safe-change
Trace, implement, test, and independently review one bounded software change. Use for ordinary feature, bug-fix, or refactor work after the repository is bootstrapped; do not use for broad repository cleanup, production operations, or undefined rewrites.