ackit-scan-and-fix

ackit-scan-and-fix is a skill for Claude Code, Codex from Cynrath/agent-context-kit. It costs 26 tokens per session (389 once invoked), scanned A, original, MIT.

A workflow for scanning a repository with ACKit and fixing the reported security findings. The scan groups issues by severity and supports visible explanations for accepted false positives.

In plain words
What is it for?
It is for auditing code, prioritising critical and high-severity findings, removing exposed keys, adding justified inline suppressions, and checking the repository again.
Why use it?
It helps find serious problems such as exposed credentials or unsafe paths and keeps exceptions documented instead of hiding them.

Skill for Claude CodeCodex

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

Good fit It is for auditing code, prioritising critical and high-severity findings, removing exposed keys, adding justified inline suppressions, and checking the repository again.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cynrath/agent-context-kit/ackit-scan-and-fix
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-scan-and-fix
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-scan-and-fix

README.md
[![agentmods](https://agentmods.dev/badge/skills/cynrath/agent-context-kit/ackit-scan-and-fix.svg)](https://agentmods.dev/skills/cynrath/agent-context-kit/ackit-scan-and-fix)
Your own site
<a href="https://agentmods.dev/skills/cynrath/agent-context-kit/ackit-scan-and-fix"><img src="https://agentmods.dev/badge/skills/cynrath/agent-context-kit/ackit-scan-and-fix.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 389 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.00026 $0.00389
Opus 5 $0.00013 $0.00195
Sonnet 5 $0.00005 $0.00078
Haiku 4.5 $0.00003 $0.00039

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

Security

Grade A, and why

ackit-scan-and-fix 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-scan-and-fix/SKILL.md · 24 lines

What it actually says

Scan and Fix

Activate when the user asks to scan, audit, or clean up the repository.

See severity playbook for triage order.

Steps

  1. ackit scan (add --ci in CI contexts; --format terminal|json|sarif|markdown|html, --baseline <file> / --write-baseline <file>, --changed / --staged / --since <ref> / --range <a..b> for incremental sets) and read findings grouped by severity (docs/reference/rules.md).
  2. Fix critical/high first: rotate exposed credentials out-of-band, remove keys, correct root-escape references. Values are never printed; do not paste findings into external services.
  3. Suppress false positives ONLY inline with # ackit-ignore:ACKITnnn <reason> on the finding line or the line above (covers that line plus the next line); every applied bypass stays visible as a non-suppressible ACKIT099 advisory. Policy-level suppressions require reason and support expiresAt; locked rules (locked: true) can never be weakened (POL-LOCKED-CONFLICT).
  4. Re-scan (ackit scan --ci) and confirm exit 0 or an explicit accepted-risk list. Confirm offline policy with ackit policy check / ackit config check where thresholds or extends changed.

Notes

  • Unknown-extension files are always scanned; do not "fix" by renaming secrets away.
  • Never weaken rules, thresholds, or baselines to make output green.
  • Resolution is offline by construction; remote fetches never happen.
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 · +1 lines baab89f30814
  2. 7d ago First seen · 23 lines · 26 tokens per session scan A c6b3fe00506e

Subscribe to this mod's changes

ackit-scan-and-fix is a skill published in the GitHub repository Cynrath/agent-context-kit (14 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 389 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