audit-context-building
Understand a codebase before looking for bugs in it - what each function assumes, what it guarantees, and what it depends on elsewhere. Use when starting an audit, threat model, or architecture review on unfamiliar code, and before any vulnerability-hunting pass.
v2026.11.12-149d7b24 installazioni+4 in 7 giorni8,2K StelleCC-BY-SA-4.0sincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install trailofbits/audit-context-buildingScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto3569c2c6…8f0a8754
3569c2c6e177…71828f0a87546 file · 10.3 KBScansioneAlto3 segnalazioni
- Caratteri invisibili o di controllo bidiresources/ANALYSIS_FORMAT.md:25
- Caratteri invisibili o di controllo bidiresources/ANALYSIS_FORMAT.md:28
- Link a domini esterni
Sorgentegithub.com/trailofbits/skills/tree/main/plugins/audit-context-building/skills/audit-context-building@149d7b2
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
Build understanding, not verdicts. This runs before anyone hunts for bugs, and feeds that work.
When to Use
At the start of an audit, a threat model, or an architecture review, when the code is unfamiliar. Also when an earlier pass produced findings nobody could judge, because no one had mapped out how the system fits together.
When NOT to Use
Do not name vulnerabilities, suggest fixes, write proofs-of-concept, or rate severity. Those belong to the hunting phase, which runs next and with the whole picture in hand. When the code counts on something and nothing checks it, record that plainly and move on — whether it matters is decided later.
Not worth the tokens on code you already understand.
Do not analyze in this context
The analysis is long, and this context needs to survive to use it. Dispatch it:
- A codebase, or more than one function — run
/audit-context-building:audit-context <path>. It orients, analyzes each function in its own subagent, and writesaudit-context/DOSSIER.mdplus one file per function underaudit-context/functions/. Only compact records return here. - A single function — dispatch the
audit-context-building:function-analyzeragent at it. It writes its prose to disk and returns a record.
Then work from what comes back: the index, the unenforced assumptions, the open questions. Read a function's file when you need its detail.
The workflow is what enforces this, not this text: a subagent bound to a return schema cannot return prose. Treat this section as routing, and route.
What comes back, and how to read it
Each record lists what must always be true (with the line that shows it), what the function takes on faith (with whatever establishes it), which functions it calls and what it needs from each, and anything still unclear. The dossier adds the rules that span several functions, who can reach what, and where the complicated parts cluster.
Two things matter more than the rest:
- Assumptions marked
nothing found. The code counts on something being true and nothing anywhere makes it true. This is the most useful thing to hand the hunting phase. - The open questions. An honest list of what is still unclear beats a confident answer that turns out to be wrong. Carry them forward instead of closing them out.
Where two records disagree, both are quoted rather than quietly reconciled. That is a fact about the code, not a flaw in the analysis.
The format
ANALYSIS_FORMAT.md defines it, and FUNCTION_MICRO_ANALYSIS_EXAMPLE.md works through examples in C and Solidity. Read them when extending this plugin or deciding whether a record can be trusted.
The format is the same whatever the target. What changes is what fills each slot, and what counts as a call you cannot see inside. DOMAIN_NOTES.md maps that across smart contracts, C and C++, decompiled firmware, and web services — read it when the target is not plain source code.
The rule that matters most: follow the calls. Whether a function is correct usually depends on something
another function does, and you cannot see that from the caller alone. A limit looks enforced because the
value came back from a function whose name suggests it was checked. So read the function being called, follow
every path through it rather than only the one that succeeds, and say what makes each assumption true. When
nothing does, use those words: nothing found. Every claim cites a line, or becomes an open question.
File di questa versione
agents/1253 B
- openai.yaml253 B
assets/13.0 KB
- trail-of-bits-mark.svg3.0 KB
resources/316.3 KB
- ANALYSIS_FORMAT.md2.6 KB
- DOMAIN_NOTES.md4.9 KB
- FUNCTION_MICRO_ANALYSIS_EXAMPLE.md8.8 KB
- SKILL.md3.9 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | Sì | Sì |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- AltaPrompt injection · Caratteri invisibili o di controllo bidiresources/ANALYSIS_FORMAT.md:25
- AltaPrompt injection · Caratteri invisibili o di controllo bidiresources/ANALYSIS_FORMAT.md:28
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.11.12-149d7b2 | 13 nov 2026 | 149d7b2 | 3569c2c6 | Firmata | – |
Altro da trailofbits
Tutto da questo editoreAltro in DFIR e threat hunting
Vai alla categoria- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
- foremostaeondave/foremost3
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login