trailmark-summary

Detect languages, count entry points, and list dependencies in codebases.

6.5k|561|Updated Jan 14, 2026

Search Tags:#code analysis #dependency analysis #summary #language detection #structural overview

Ready to run

npx skills add https://github.com/trailofbits/skills --skill trailmark-summary-trailofbits

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trailmark-summary
Source: https://github.com/trailofbits/skills/tree/main/plugins/trailmark/skills/trailmark-summary
Command: npx skills add https://github.com/trailofbits/skills --skill trailmark-summary-trailofbits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Provides a rapid assessment of a codebase, identifying auto-detected languages, entry point count, and dependencies without a full structural analysis.

Core Features & Use Cases

Language Detection: Automatically determines the programming languages in a codebase.
Entry Points Count: Counts state-changing entry points in the code for security auditing.
Dependency List: Provides a list of dependencies within the codebase.
Use Case: Use when a quick understanding of a codebase's structure is needed, for instance, before decomposing or deep analysis.

Quick Start

To analyze the codebase located in '/path/to/codebase', run:

trailmark-summary /path/to/codebase

Frequently Asked Questions about trailmark-summary

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

FAQPage Schema

How do I get a structural overview of a codebase for security analysis?▼

To get a structural overview of a codebase for security analysis, you can automatically detect programming languages, count state-changing entry points, and list dependencies without performing a full deep structural analysis.

How do I detect programming languages and list dependencies in a codebase?▼

You can detect programming languages and list dependencies in a codebase by running a rapid structural assessment tool that parses the directory and aggregates the project's dependency information.

What is the best way to count state-changing entry points in a codebase?▼

The best way to count state-changing entry points in a codebase is to use an automated code analysis tool that identifies and tallies these entry points during a rapid structural assessment for security workflows.

Do I need a specific tool to generate a codebase summary and structural overview?▼

Yes, generating a codebase summary requires the trailmark tool with parse API access, along with Bash, Grep, and Glob access to properly detect languages and count entry points.

When should I use a rapid codebase summary instead of a full structural analysis?▼

You should use a rapid codebase summary instead of a full structural analysis when you need to quickly understand a codebase's structure, such as before decomposing the project or starting deep analysis.