tob-audit-context

Builds deep architectural context of a codebase before vulnerability hunting.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill tob-audit-context-ayoub-ouederni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tob-audit-context
Source: https://github.com/Ayoub-ouederni/SENTINEL/tree/main/.claude/skills/tob-audit-context
Command: npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill tob-audit-context-ayoub-ouederni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security auditors often jump into vulnerability hunting without sufficient understanding of a codebase's architecture, leading to missed issues and shallow findings. This Skill builds deep architectural context first, so subsequent audit work is grounded in how the system actually fits together. ## Core Features & Use Cases - Codebase Context Building: Analyzes a target codebase path to construct architectural understanding before auditing. - Focused Module Analysis: Accepts an optional --focus <module> argument to concentrate analysis on a specific module. - Workflow Delegation: Invokes the audit-context-building skill to execute the full context-building workflow. - Use Case: Before auditing a smart contract repository, run this Skill on the codebase path with --focus contracts to establish architectural context that guides later vulnerability hunting. ## Quick Start Ask the assistant to build audit context for your codebase by providing the repository path, optionally specifying a module to focus on.

Frequently Asked Questions about tob-audit-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build architectural context before a security audit?

Provide the path to the codebase you want to analyze, and the Skill constructs deep architectural context before vulnerability hunting. You can narrow the scope with the --focus option followed by a module name.

How do I focus an audit context analysis on one module?

Pass the --focus flag followed by the module name after the codebase path. This restricts the context-building analysis to that specific module instead of the entire codebase.

What arguments does the audit context skill require?

It requires a codebase path as the first argument. The --focus <module> argument is optional and enables targeted analysis of a specific module within the codebase.

When should I build audit context instead of hunting vulnerabilities directly?

Build context first when auditing unfamiliar or large codebases, since architectural understanding prevents shallow findings. Direct vulnerability hunting suits small, well-understood codebases where structure is already known.