codebase-navigation — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited codebase-navigation (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An agent that can quickly orient itself in any codebase - finding the right files, understanding the architecture, and identifying conventions - before writing a single line of code. Agents without this skill guess at file locations, miss existing utilities, and create duplicates.
Before touching code, build a mental map:
README.md, CONTRIBUTING.md, and any project-level config filespackage.json, pyproject.toml, Cargo.toml, go.mod)Infer the project's conventions from existing code:
__tests__ directory, naming patternsTrace how components connect:
Use the right tool for each search type:
| Goal | Strategy |
|---|---|
| Find a file by name | Glob patterns: **/UserService.*, **/*.config.* |
| Find where a function is defined | Grep for function name( or def name or class Name |
| Find where a function is called | Grep for the function name, exclude the definition file |
| Understand data flow | Start at the API endpoint, follow the handler chain inward |
| Find related tests | Look for files matching *.test.*, *.spec.*, or test_* near the source |
Identify common architectural patterns:
services/ or separate packages with their own entry pointspackages/ or apps/ directory with shared librariesfunctions/ or lambdas/, infrastructure as code nearby| Failure | Symptom | Correction |
|---|---|---|
| Skipping reconnaissance | Creating files in wrong locations | Always map the project before writing |
| Ignoring conventions | Code looks foreign in the PR diff | Read 3-5 existing files in the same area first |
| Shallow search | Missing existing utilities, creating duplicates | Search by concept, not just by exact name |
| Assuming structure | "I expect a utils/ folder" when the project uses lib/shared/ | Let the project tell you its structure |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.