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 coding-agentgit 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/coding-agent)<a href="https://agentmods.dev/skills/codeinfinity1/stram/coding-agent"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/coding-agent/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/coding-agent"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/coding-agent.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.00026 | $0.00644 |
| Opus 5.5 | $0.00010 | $0.00258 |
| Sonnet 5.5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
coding-agent 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Agent Delegation
Purpose
Coordinate bounded coding work through native Codex CLI and multi-agent tools while preserving user changes, test evidence, and explicit completion reporting.
Tool Map
codex_cli_statuscodex_cli_plancodex_cli_runmulti_agent_coordinatemulti_agent_board
Use this skill for background feature builds, code reviews, large refactors, and issue-to-PR loops. Do not use it for simple edits or read-only lookup.
When To Delegate
Delegate when the work is:
- bounded and testable;
- repository-local;
- long enough to benefit from a separate worker;
- safe to run in the chosen sandbox;
- not dependent on secrets or private context the worker does not need.
Required Steps
- Check CLI availability with
codex_cli_statusor a shell command. - Prepare a prompt that includes:
- objective;
- repo path;
- files or modules likely involved;
- constraints;
- expected tests;
- how to report completion.
- Use
codex_cli_planwhen available to prepare the handoff. - Use
codex_cli_runonly when the user requested implementation or verification that fits delegation. - Verify important claims locally after the worker completes.
Workflow
- Decide whether delegation is warranted or whether the current agent should do the work directly.
- Check
codex_cli_statusand current repository state. - Build a scoped handoff with
codex_cli_planormulti_agent_coordinate. - Use
codex_cli_runonly after reviewing the generated task, sandbox, and approval requirements. - Re-read local git status, diffs, and relevant files after completion.
- Run focused verification locally before accepting the worker's result.
Prompt Shape
Include:
Task:
<clear objective>
Workspace:
<absolute repo path>
Constraints:
- preserve user changes
- do not store secrets
- keep edits scoped
- run listed tests
Completion:
- summarize files changed
- report test output
- report blockers
Safety
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 · 97 lines · 26 tokens per session scan A 270526c471ee
coding-agent is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 644 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…