assess-verification

assess-verification is a skill for Claude Code from krokoko/cairn. It costs 53 tokens per session (4,039 once invoked), scanned A, original, Apache-2.0.

A codebase assessment skill that reviews how a project checks its software and reports its verification maturity. Verification includes tests and other ways to detect incorrect, unsafe, or broken code.

In plain words
What is it for?
Use it to audit tests and other verification tools, assess coverage and feedback loops, identify missing checks, and create a verification report.
Why use it?
It reveals gaps such as missing tests, weak checks, unclear expected results, or steps that still require human review. This makes it easier to decide what should be checked automatically before changes are accepted.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the software-verification plugin — 3 skills shipped together

Good fit Use it to audit tests and other verification tools, assess coverage and feedback loops, identify missing checks, and create a verification report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/krokoko/cairn/assess-verification
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 krokoko/cairn --skill assess-verification
Clone the repo
git clone --depth 1 https://github.com/krokoko/cairn

Made for: Claude Code.

Or install software-verification, the plugin that ships this one along with the rest of its 3 skills.

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 assess-verification

README.md
[![agentmods](https://agentmods.dev/badge/skills/krokoko/cairn/assess-verification/github.svg)](https://agentmods.dev/skills/krokoko/cairn/assess-verification)
Your own site
<a href="https://agentmods.dev/skills/krokoko/cairn/assess-verification"><img src="https://agentmods.dev/badge/skills/krokoko/cairn/assess-verification/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.

agentmods 80×15 button for assess-verification

Your own site · 80×15
<a href="https://agentmods.dev/skills/krokoko/cairn/assess-verification"><img src="https://agentmods.dev/badge/skills/krokoko/cairn/assess-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,039 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.00053 $0.04039
Opus 5 $0.00026 $0.02020
Sonnet 5 $0.00011 $0.00808
Haiku 4.5 $0.00005 $0.00404

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

Security

Grade A, and why

assess-verification 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.

plugins/software-verification/skills/assess-verification/SKILL.md · 326 lines

How it starts

The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Software Verification Assessment

Assess the current verification maturity of a codebase. Produce a verification-report.md with maturity tier, component breakdown, missing oracles, exactness analysis, human review requirements, autonomy candidates, feedback loop completeness, workflow gate assessment, and shift-left positioning.

Workflow

Step 1: Inventory existing verification

Search for all verification-related artifacts:

Testing:

  • Test files: *_test.*, *_spec.*, test_*.*, tests/, __tests__/
  • Test config: jest.config.*, pytest.ini, pyproject.toml [tool.pytest], vitest.config.*
  • Property tests: imports of hypothesis, fast-check, proptest, QuickCheck
  • Fuzzing: fuzz/, *_fuzz_test.go, cargo-fuzz config, AFL configs
  • Mutation testing: mutmut, stryker.conf.*, cargo-mutants config

Static analysis:

  • Linters: .eslintrc*, ruff.toml, .golangci.yml, clippy.toml
  • Type checkers: tsconfig.json, mypy.ini, pyrightconfig.json
  • SAST tools: .semgrep/, codeql-config.yml
  • Sanitizers: ASan/TSan/UBSan flags in build configs or CI
  • Profiling: pprof, perf, py-spy configurations or scripts

Security and supply chain:

  • Dependency / SCA scanning: Dependabot (.github/dependabot.yml), Renovate, Snyk, npm audit, pip-audit, osv-scanner, govulncheck in CI
  • Secret scanning: gitleaks, detect-secrets, trufflehog configs or hooks
  • IaC scanning: tfsec, checkov, kics, terrascan configs or CI steps

Contracts and schemas:

  • Schemas: *.schema.json, *.proto, openapi.*, *.graphql
  • Contracts: assertions, icontract, contracts library imports, invariant
  • Consumer-driven contracts: pact/, pacts/, Pact broker config, Spring Cloud Contract stubs
  • Formal specs: *.tla, *.cfg (TLC), *.als, *.dfy

CI and operational:

  • CI config: .github/workflows/, .gitlab-ci.yml
  • Coverage: codecov.yml, coverage report configs
  • Canary/shadow: feature flag configs, deployment configs, traffic splitting

Read the full file on GitHub · 326 lines

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. 9d ago First seen · 326 lines · 53 tokens per session scan A d59f1d6254c5

Subscribe to this mod's changes

assess-verification is a skill published in the GitHub repository krokoko/cairn (14 stars, last pushed 5d ago), licensed Apache-2.0. It adds 53 tokens to every session and 4,039 once invoked, about $0.0003 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.