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 agentmods add skills/codename-11/subframe/releasenpx skills add Codename-11/SubFrame --skill releasegit clone --depth 1 https://github.com/Codename-11/SubFrameWhat 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 | $0.00017 | $0.01228 |
| Opus 5 | $0.00009 | $0.00614 |
| Sonnet 5 | $0.00003 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
release 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 2d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Procedure
Create a release for SubFrame. The argument specifies the version bump type or an explicit version number.
Dynamic Context
Current version (from package.json):
!node -e "console.log(require('./package.json').version)"
Last 5 tags:
!git tag --sort=-v:refname | head -5
Recent commits (last 30):
!git log --oneline --no-decorate -30
Current branch:
!git branch --show-current
Working tree clean?
!git status --porcelain
Instructions
Argument: $ARGUMENTS
Pre-flight Checks
- Verify clean working tree — if there are uncommitted changes, STOP and warn the user. Releases must be made from a clean state.
- Verify on main branch — warn if not on
main. - Verify build succeeds — run
npm run buildand confirm it completes without errors.
Step 1: Determine Version
Parse the argument:
patch— bump PATCH, keep-betasuffix (e.g.,0.2.0-beta→0.2.1-beta)minor— bump MINOR, reset PATCH, keep-betasuffix (e.g.,0.2.1-beta→0.3.0-beta)major— bump MAJOR, reset MINOR+PATCH, drop-betato produce first stable release (e.g.,0.3.0-beta→1.0.0)stable— strip-betasuffix without changing version numbers (e.g.,0.3.0-beta→0.3.0)x.y.zorx.y.z-beta(explicit) — use as-is, validate it's greater than current- No argument — analyze the commits since last tag and recommend a bump:
- Any
feat!,fix!, orBREAKING CHANGE-> MAJOR (goes stable) - Any
feat-> MINOR - Only
fix/docs/perf/chore/refactor-> PATCH - Ask the user to confirm before proceeding
- Any
Beta versioning scheme: All 0.x.y versions use the -beta suffix (no numeric counter). The -beta suffix is preserved on patch/minor bumps and only dropped when going stable via major or stable.
Step 2: Update package.json
Update the "version" field in package.json to the new version string. This is the single source of truth — FRAME_VERSION in src/shared/frameConstants.js reads from it automatically via require().
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.
- 2d ago First seen · 118 lines · 17 tokens per session scan A ea6d65173c4f
release is a skill published in the GitHub repository Codename-11/SubFrame (10 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 1,228 once invoked, about $0.0001 per session on Opus 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
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
intuitive-flow
Stable execution/change router after an approved plan, preflight contract, or tiny concrete task. Refactor-shaped work delegates to intuitive-refactor, and durable work runs through staged planning, review, GSD handoff, implementation, cleanup, and verification while keeping plan ledgers and active capsules compact by…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
cross-review
Challenge an existing agent proposal through a small bounded set of independent review perspectives, then judge the findings into one simpler or more defensible recommendation. Use immediately after an agent proposes a solution when the user asks whether there is a simpler approach, wants a second opinion or other…
multica-goal-tracker
Track goal-driven Multica issues. Use when a user creates or maintains Multica issues by pasting a /goal prompt, wants Codex to summarize that goal into a concise issue purpose, append a normalized goal-start comment, record completion evidence from real Multica execution run messages or a supplied session transcript…