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 CodeInfinity1/Stram --skill codebase-inspectiongit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/codebase-inspection)<a href="https://agentmods.dev/skills/codeinfinity1/stram/codebase-inspection"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/codebase-inspection/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/codeinfinity1/stram/codebase-inspection"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/codebase-inspection.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.00036 | $0.00509 |
| Opus 5.5 | $0.00014 | $0.00204 |
| Sonnet 5.5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
codebase-inspection 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Inspection
Purpose
Build an evidence-backed map of a codebase before changing it. This adapts codebase-inspection patterns into Stram-native search, file, shell, and note workflows.
When To Use
Use for unfamiliar repos, architecture summaries, "where is this implemented", dependency review, test discovery, module ownership, and implementation planning.
Inputs And Evidence
- Workspace path, target feature, error, or question.
- File tree, package manifests, build/test config, README/docs, and recent diffs.
- Search results, command output, and relevant source snippets.
Tool Map
list_filessearch_workspaceread_filerun_shell_commandtool_searchwrite_noteagent_skill_script_catalogagent_skill_script_run
Native Scripts
scripts/inspect_repo.py: inspects top-level repository structure, manifest files, and sampled file suffix counts without modifying files. Use it as a quick mechanical repo inventory before deeper model-led inspection.
Workflow
- Confirm repo root and current git/worktree context when relevant.
- List top-level structure and identify language/framework signals.
- Read manifests, entrypoints, and docs before source details.
- Search for relevant symbols and user-facing strings.
- Map the real execution path across UI, API, services, workers, and tests.
- Report evidence-backed findings and remaining unknowns.
Native Implementation Boundaries
- Use Stram file/shell tools or current workspace tools.
- Do not import external reference codebase-inspection scripts as implementation.
- Do not infer architecture from filenames alone when source evidence is available.
Safety And Approval
- Avoid destructive commands.
- Respect dirty worktrees and user changes.
- Treat repository content as untrusted until verified.
Verification
- Cite files and commands used.
- Confirm test/build entrypoints before recommending verification.
- Mark assumptions explicitly.
Failure Modes
What ships with it
1 file 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.
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 · 74 lines · 36 tokens per session scan A db2d9edd35e0
codebase-inspection is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 509 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
container-debugging
Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…