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 agent-self-assessmentgit 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/agent-self-assessment)<a href="https://agentmods.dev/skills/codeinfinity1/stram/agent-self-assessment"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/agent-self-assessment/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/agent-self-assessment"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/agent-self-assessment.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.00048 | $0.00664 |
| Opus 5.5 | $0.00019 | $0.00266 |
| Sonnet 5.5 | $0.00010 | $0.00133 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
agent-self-assessment 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Self Assessment
Purpose
Create an explicit readiness check before the assistant commits to complex action. This skill combines external reference agent audit and self-assessment ideas with Stram capability, tool, policy, and cognition surfaces.
When To Use
Use for high-impact tasks, broad architecture changes, long autonomous runs, external integrations, multi-agent work, or when the assistant is unsure whether it has enough tools and context.
Inputs And Evidence
- Capability surface and tool descriptions.
- Current workspace state and relevant files.
- Model provider readiness.
- Safety policy and approval requirements.
- Known blockers, memory, and environment constraints.
Tool Map
capability_surfacetool_searchtool_describecognitive_self_reviewcognitive_environment_statussystem_statusplugin_catalogchannel_catalog
Workflow
- Clarify the objective and expected end state.
- Inspect capability surface and relevant tool schemas.
- Identify missing credentials, missing tools, policy gates, and high-risk actions.
- Decide whether to proceed, narrow scope, ask for input, or run a safer dry run.
- Define verification evidence before execution.
- Reassess after failures or surprising tool output.
Safety And Boundaries
- Do not use assessment as a substitute for doing safe, obvious work.
- Do not downplay risks when tools can affect external systems.
- If a model/provider is unavailable, stop or use explicit tool commands only; do not invent deterministic intent handling.
Safety And Approval
- Treat self-assessment as advisory evidence, not permission to bypass approval gates.
- If the assessment identifies external-visible, destructive, privileged, or privacy-sensitive actions, require the relevant tool approval before execution.
- Do not downgrade risk because a task is familiar; use current tool schemas, provider status, credentials, and workspace state.
- Report model-unavailable or tool-unavailable states honestly instead of substituting brittle keyword rules.
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 · 80 lines · 48 tokens per session scan A b5dce37429ef
agent-self-assessment is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 664 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…