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 skill-authoringgit 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/skill-authoring)<a href="https://agentmods.dev/skills/codeinfinity1/stram/skill-authoring"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/skill-authoring/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/skill-authoring"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/skill-authoring.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.00044 | $0.00827 |
| Opus 5.5 | $0.00018 | $0.00331 |
| Sonnet 5.5 | $0.00009 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
skill-authoring 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Authoring
Purpose
Author high-quality Stram skills that follow the project standard and can be selected by model-led planning. This adapts external reference skill authoring and Anthropic skill-creator guidance.
When To Use
Use when creating new skills, improving existing skills, integrating upstream skill ideas, adding scripts/references, or validating the skill library.
Inputs And Evidence
docs/AGENT_SKILL_AUTHORING_STANDARD.md.- Source skill text or catalog entries from trusted local references.
- Current tool catalog and capability surface.
- Existing skills to avoid duplication.
- User's requested domain and scope.
Tool Map
agent_skill_catalogagent_skill_readagent_skill_script_catalogagent_skill_script_readagent_skill_script_runskill_forge_draftskill_forge_packscognitive_skill_evolveread_filesearch_workspacerun_shell_command
Workflow
- Read the authoring standard before editing or generating skills.
- Search existing skills for overlap and decide whether to update or create.
- Use upstream material only as reference evidence; write Stram-owned guidance.
- Ensure every required tool, script, adapter, or helper is native to Stram or already exposed through a trusted Stram platform tool.
- If upstream material implies a missing tool, record the gap or implement a Stram-owned tool; do not depend on external reference, external reference, Anthropic Skills, external skill catalog, or Codex plugin code directly.
- Create valid frontmatter: lowercase hyphenated
name, description under 1024 chars, optional compatibility/license/metadata. - Include purpose, when-to-use, evidence, tool map, workflow, safety, verification, failure modes, and references.
- Add
scripts/,references/, orassets/only when they improve execution or progressive disclosure and are Stram-owned. - For each native script, add first-line metadata, enforce allowed root boundaries, accept the standard JSON envelope, emit bounded JSON output when possible, and list it under
Native Scripts. - Run the workspace skill format and skill-tool tests.
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 · 83 lines · 44 tokens per session scan A 851712e41da3
skill-authoring is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 827 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-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…