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 capability-auditgit 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/capability-audit)<a href="https://agentmods.dev/skills/codeinfinity1/stram/capability-audit"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/capability-audit/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/capability-audit"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/capability-audit.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.00049 | $0.00634 |
| Opus 5.5 | $0.00020 | $0.00254 |
| Sonnet 5.5 | $0.00010 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
capability-audit 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capability Audit
Purpose
Give the user and model an evidence-backed map of what the assistant can actually do now. This skill adapts external reference agent audit patterns to Stram's capability surface and plugin catalogs.
When To Use
Use before large architecture changes, after adding tools/skills/plugins, when debugging "is this wired?", or when choosing the next integration batch.
Inputs And Evidence
capability_surfacerecords.- Tool catalog and descriptions.
- Workspace skill catalog and memory skills.
- Per-skill capability audit matrix.
- Plugin and channel catalogs.
- Provider readiness for OpenAI, Groq, Ollama, voice, browser, and OS tools.
- Recent smoke test artifacts.
Tool Map
capability_surfacetool_searchtool_describeagent_skill_catalogagent_skill_capability_auditplugin_catalogchannel_catalogvoice_provider_statusexternal_integrations_statussystem_status
Workflow
- Gather the current capability surface with records included when useful.
- Run
agent_skill_capability_auditwhen the question includes skill completeness, prompt-only skills, live readiness, or smoke coverage. - Count tools, skills, channels, providers, plugins, and notable missing surfaces.
- Verify readiness for local services and cloud providers before claiming availability.
- Compare current capabilities to the user's requested architecture or shortlist.
- Identify gaps as missing, partially wired, untested, blocked by credentials, or blocked by policy.
- Recommend the next implementation batch with verification steps.
Safety
- Do not claim a provider is usable because config exists; use status or smoke evidence.
- Do not treat catalog declarations as direct execution support.
- Keep external secrets redacted.
Native Implementation Boundaries
- Use
capability_surface,tool_search,tool_describe, catalogs, and status tools as authoritative current-state inputs. - Use
agent_skill_capability_auditfor skill implementation status; do not classify skills from informal names or reference repos. - Report live readiness separately from native local support when credentials, CLIs, local models, or network access are unavailable.
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 · 79 lines · 49 tokens per session scan A 00306fb450b6
capability-audit is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 634 once invoked, about $0.0002 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-08-31.
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…