ackit-policy-authoring

ackit-policy-authoring is a skill for Claude Code, Codex from Cynrath/agent-context-kit. It costs 23 tokens per session (399 once invoked), scanned A, original, MIT.

A workflow for writing layered ackit policy files, which are configuration files that define how code or security scans should be applied. Policies can set rules by organization, repository, or path.

In plain words
What is it for?
Setting scan thresholds, adding scoped rule overrides, locking security rules, documenting suppressions, and checking the resulting policy digest.
Why use it?
It makes scan rules consistent and prevents important security rules from being weakened by downstream projects. It also keeps policy dependencies local and offline.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Setting scan thresholds, adding scoped rule overrides, locking security rules, documenting suppressions, and checking the resulting policy digest.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cynrath/agent-context-kit/ackit-policy-authoring
Install

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.

Any agent
npx skills add Cynrath/agent-context-kit --skill ackit-policy-authoring
Clone the repo
git clone --depth 1 https://github.com/Cynrath/agent-context-kit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ackit-policy-authoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/cynrath/agent-context-kit/ackit-policy-authoring.svg)](https://agentmods.dev/skills/cynrath/agent-context-kit/ackit-policy-authoring)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 399 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00399
Opus 5 $0.00012 $0.00199
Sonnet 5 $0.00005 $0.00080
Haiku 4.5 $0.00002 $0.00040

Measured 2d ago against content hash 14af96adcbfe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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 2d 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.

templates/skills/ackit-policy-authoring/SKILL.md · 24 lines

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

  1. Start from ackit.yml; add a policy layer with schemaVersion: 1 and extends (local repo-relative files or npm:<pkg>/<file> for already-installed packages only — resolution is offline by construction, remote fetch is refused with POL-OFFLINE-BLOCKED).
  2. Scope overrides with org / repo / pathScopes; lock security-relevant rules with locked: true so downstream layers cannot weaken them (POL-LOCKED-CONFLICT; deny is sticky across layers). Suppressions require reason and support expiresAt.
  3. Verify with ackit policy check (chain plus digest plus autonomy plus review plus problems) and ackit config check (schema validation). Risk tiers (tier0 allow through tier4 deny) enforce ONLY at ACKit-owned boundaries (task complete --force, checkpoint export, verification record): explicit deny refuses with POLICY-TIER-DENIED (exit 4); explicit ask in a non-interactive context denies. Optional review: (required dimensions plus blockingSeverity) gates PASS-family verdicts via VERDICT_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.
Files

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.

Changes

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.

  1. 2d ago Changed 14af96adcbfe
  2. 7d ago First seen · 24 lines · 23 tokens per session scan A 0381477aa92a

Subscribe to this mod's changes

ackit-policy-authoring is a skill published in the GitHub repository Cynrath/agent-context-kit (14 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 399 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.

Related

Other skills, from other repositories

opensrc

Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…

vercel-labs/opensrc · 103 tokens

agentplane-release-and-packaging-operator

Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.

basilisk-labs/agentplane · 60 tokens

agentplane-task-closure-recovery

Use when Agentplane task completion, direct finish, branchpr integration, hosted-close, close-tail PRs, PR metadata, dirty task artifacts, or remote branch divergence need diagnosis or recovery.

basilisk-labs/agentplane · 46 tokens

agentplane-testkit-migration

Use when migrating Agentplane tests to @agentplane/testkit, replacing local test helpers, fixing testkit export/build failures, splitting large CLI/backend suites, or diagnosing missing testkit dist exports in package builds.

basilisk-labs/agentplane · 49 tokens

agentplane-local-dev-operator

Use when accelerating AgentPlane framework development, selecting targeted local checks, validating branchpr task scope, using the Turborepo local graph, or triaging dependency bumps before merge or release.

basilisk-labs/agentplane · 45 tokens

qamap-pr-qa

Local zero-LLM PR QA workflow. Use when an agent is preparing, updating, finalizing, or reviewing a pull request, asks what the PR should test, or needs commit-backed change intent, affected behavior, QA scenarios, evidence, validation commands, optional automation drafts, and manifest repair guidance.

IvoryCanvas/QAMap · 67 tokens