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 samibs/skillfoundry --skill versiongit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/version)<a href="https://agentmods.dev/skills/samibs/skillfoundry/version"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/version.svg" alt="Measured on agentmods" 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.00004 | $0.03844 |
| Opus 5 | $0.00002 | $0.01922 |
| Sonnet 5 | $0.00001 | $0.00769 |
| Haiku 4.5 | $0.00000 | $0.00384 |
Grade B, and why
version scanned grade B with 1 finding 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 yesterday.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/.framework-version How it starts
The opening of the file, as written. The whole thing — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: version description: Show version information and check for updates
You are the Version Information Agent. Display current version, check for updates, and explain version semantics.
Version Format
Claude AS uses semantic versioning: MAJOR.FEATURE.DATABASE.ITERATION
1.7.0.0
│ │ │ └─ Iteration (patches, bug fixes)
│ │ └─── Database (schema changes, migrations)
│ └───── Feature (new features, enhancements)
└─────── Major (breaking changes)
Version Component Meanings
| Component | Changes | Update Type | Risk Level |
|---|---|---|---|
| MAJOR | Breaking changes, new architecture | Fresh install required | HIGH |
| FEATURE | New agents, capabilities, workflows | Safe update | LOW |
| DATABASE | Schema changes, data migrations | Migration required | MEDIUM |
| ITERATION | Bug fixes, patches, minor improvements | Safe update | VERY LOW |
Commands
Parse user input for mode:
/version- Show current version and check for updates/version --check- Check for updates only/version --info- Detailed version information/version --history- Show version history (changelog)
Version Detection
-
Detect platform (Claude Code, Copilot CLI, or Cursor)
- Claude Code: Check
~/.claude/.framework-version - Copilot CLI: Check
~/.copilot/.framework-version - Cursor: Check
~/.cursor/.framework-version
- Claude Code: Check
-
Get installed version
cat ~/.claude/.framework-version -
Get available version
cat /path/to/framework/.version -
Compare versions Use
scripts/version-check.shfor comparison logic
Version Display Format
╔═══════════════════════════════════════════════════════════════╗
║ Claude AS Framework ║
╠═══════════════════════════════════════════════════════════════╣
║ Version: 1.7.0.0 ║
║ ║
║ 1 - Major Version (Breaking changes) ║
║ 7 - Feature Version (New features) ║
║ 0 - Database Version (Schema changes) ║
║ 0 - Iteration (Patches/bug fixes) ║
╚═══════════════════════════════════════════════════════════════╝
═══════════════════════════════════════════════════════════════
VERSION INFORMATION
═══════════════════════════════════════════════════════════════
Installed Version: 1.7.0.0
Available Version: 1.7.0.0
✓ Status: Up to date
No action needed
═══════════════════════════════════════════════════════════════
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.
- yesterday Changed · +1 lines 0291bd0cd1ef
- 2d ago Changed · +1 lines ecbacd2c444f
- 3d ago First seen · 412 lines · 4 tokens per session scan B 2a7483f853ce
version is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 2d ago), licensed MIT. It adds 4 tokens to every session and 3,844 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
forge-execute
Guided plan execution — list available plans, estimate cost, choose mode, and execute with live progress. Use when you want to run a hardened plan through the orchestrator.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
ring:managing-dev-cycle
Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip…
ring:validating-acceptance-criteria
Validating a completed task against its acceptance criteria, mapping each AC to evidence, and gating completion on explicit user sign-off (self-approval prohibited). Gate 5 of ring:running-dev-cycle / ring:running-dev-cycle-frontend, run at task cadence after ring:reviewing-code. Use when implementation and tests are…
ring:writing-dev-reports
Writing a structured markdown dev report for a completed development epic: reads accumulated epic metrics (TDD, coverage, delivery, lint, file-size, license), computes a quality score with tiers, and records root-cause and next-cycle improvements. Use after an epic completes in ring:running-dev-cycle or when asked for…
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.