functionality-audit

functionality-audit is a skill for Claude Code, Codex from DNYoussef/context-cascade. It costs 0 tokens per session (1,944 once invoked), scanned A, a copy of dogfooding-system, MIT.

A verification workflow that checks whether generated or modified code actually runs correctly by testing it in a controlled environment.

In plain words
What is it for?
Use it after writing or changing code to run checks, verify behaviour, and investigate failures.
Why use it?
It reduces the risk of accepting code that looks correct but fails when executed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the TodoWrite tool.

Good fit Use it after writing or changing code to run checks, verify behaviour, and investigate failures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dnyoussef/context-cascade/functionality-audit
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 DNYoussef/context-cascade --skill functionality-audit
Clone the repo
git clone --depth 1 https://github.com/DNYoussef/context-cascade

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 functionality-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/dnyoussef/context-cascade/functionality-audit/github.svg)](https://agentmods.dev/skills/dnyoussef/context-cascade/functionality-audit)
Your own site
<a href="https://agentmods.dev/skills/dnyoussef/context-cascade/functionality-audit"><img src="https://agentmods.dev/badge/skills/dnyoussef/context-cascade/functionality-audit/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 functionality-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/dnyoussef/context-cascade/functionality-audit"><img src="https://agentmods.dev/badge/skills/dnyoussef/context-cascade/functionality-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,944 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 86% copy Near-identical to another mod 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.00000 $0.01944
Opus 5.5 $0.00000 $0.00778
Sonnet 5.5 $0.00000 $0.00389
Haiku 4.5 $0.00000 $0.00194

Measured 1mo ago against content hash afbfb7fc492c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

functionality-audit 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.

The scan reads SKILL.md. This mod also ships 4 executable files (resources/examples/example_usage.py, resources/scripts/sandbox_manager.sh, resources/scripts/test_generator.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

86% identical to dogfooding-system — 53 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.

skills/quality/functionality-audit/SKILL.md · 201 lines

How it starts

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

/============================================================================/ /* FUNCTIONALITY-AUDIT SKILL :: VERILINGUA x VERIX EDITION / /============================================================================*/


name: functionality-audit version: 1.1.0 description: | [assert|neutral] Validates that code actually works through sandbox testing, execution verification, and systematic debugging. Use this skill after code generation or modification to ensure functionality is genuine ra [ground:given] [conf:0.95] [state:confirmed] category: quality tags:

  • quality
  • testing
  • validation author: ruv cognitive_frame: primary: evidential goal_analysis: first_order: "Execute functionality-audit workflow" second_order: "Ensure quality and consistency" third_order: "Enable systematic quality processes"

/----------------------------------------------------------------------------/ /* S0 META-IDENTITY / /----------------------------------------------------------------------------*/

[define|neutral] SKILL := { name: "functionality-audit", category: "quality", version: "1.1.0", layer: L1 } [ground:given] [conf:1.0] [state:confirmed]

/----------------------------------------------------------------------------/ /* S1 COGNITIVE FRAME / /----------------------------------------------------------------------------*/

[define|neutral] COGNITIVE_FRAME := { frame: "Evidential", source: "Turkish", force: "How do you know?" } [ground:cognitive-science] [conf:0.92] [state:confirmed]

Kanitsal Cerceve (Evidential Frame Activation)

Kaynak dogrulama modu etkin.

/----------------------------------------------------------------------------/ /* S2 TRIGGER CONDITIONS / /----------------------------------------------------------------------------*/

[define|neutral] TRIGGER_POSITIVE := { keywords: ["functionality-audit", "quality", "workflow"], context: "user needs functionality-audit capability" } [ground:given] [conf:1.0] [state:confirmed]

/----------------------------------------------------------------------------/ /* S3 CORE CONTENT / /----------------------------------------------------------------------------*/

Read the full file on GitHub · 201 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. 1mo ago First seen · 201 lines · 0 tokens per session scan A afbfb7fc492c

Subscribe to this mod's changes

functionality-audit is a skill published in the GitHub repository DNYoussef/context-cascade (32 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,944 tokens. A static security scan graded it A with 0 findings. It is 86% identical to dogfooding-system, differing in 53 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

4-phase root cause debugging: understand bugs before fixing.

NousResearch/hermes-agent · 16 tokens

langsmith-observability

LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.

davila7/claude-code-templates · 45 tokens

test-failure-explorer

Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.

QwenLM/qwen-code · 32 tokens

experimental-code-coverage-local-debugger

Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.

chromium/chromium · 59 tokens

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

cli-e2e

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

ComposioHQ/composio · 62 tokens