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 DNYoussef/context-cascade --skill functionality-auditgit clone --depth 1 https://github.com/DNYoussef/context-cascadeWrote 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/dnyoussef/context-cascade/functionality-audit)<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.
<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>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.00000 | $0.01944 |
| Opus 5.5 | $0.00000 | $0.00778 |
| Sonnet 5.5 | $0.00000 | $0.00389 |
| Haiku 4.5 | $0.00000 | $0.00194 |
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.
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.
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.
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 / /----------------------------------------------------------------------------*/
What ships with it
32 files 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.
- examples/example-1-basic-validation.md 11 KB
- examples/example-2-integration-testing.md 15 KB
- examples/example-3-debugging-race-condition.md 20 KB
- functionality-audit-process.dot 4.0 KB
- graphviz/creation-summary.md 12 KB
- graphviz/debugging-decision-tree.dot 9.5 KB
- graphviz/functionality-audit-process.dot 4.0 KB
- graphviz/index.md 9.6 KB
- graphviz/quick-reference.md 1.8 KB
- graphviz/readme.md 6.9 KB
- graphviz/TREE.txt 127 B
- graphviz/workflow.dot 5.6 KB
- manifest.json 1.5 KB
- readme.md 12 KB
- references/best-practices.md 15 KB
- references/related-skills.md 17 KB
- references/troubleshooting.md 19 KB
- resources/creation-summary.md 13 KB
- resources/examples/example_usage.py 7.4 KB runs code
- resources/quick-reference.md 7.4 KB
- resources/readme.md 14 KB
- resources/scripts/sandbox_manager.sh 13 KB runs code
- resources/scripts/test_generator.py 19 KB runs code
- resources/scripts/validate_code.py 21 KB runs code
- resources/STRUCTURE.txt 5.0 KB
- resources/templates/sandbox-config.json 6.4 KB
- resources/templates/validation-report.yaml 3.8 KB
- tests/readme.md 7.5 KB
- tests/test-basic-validation.md 6.6 KB
- tests/test-bug-detection.md 9.4 KB
- tests/test-edge-case-coverage.md 19 KB
- tests/test-integration-failure.md 16 KB
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 First seen · 201 lines · 0 tokens per session scan A afbfb7fc492c
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.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
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.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
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.
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.…
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.