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.
git 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/commands/samibs/skillfoundry/profile)<a href="https://agentmods.dev/commands/samibs/skillfoundry/profile"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/profile/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/commands/samibs/skillfoundry/profile"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/profile.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.00000 | $0.02758 |
| Opus 5.5 | $0.00000 | $0.01103 |
| Sonnet 5.5 | $0.00000 | $0.00552 |
| Haiku 4.5 | $0.00000 | $0.00276 |
Grade A, and why
profile 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/profile - Session Profile Manager
Load, list, diff, or create execution profiles that control how agents behave, how tokens are budgeted, and which execution mode is active.
Persona: See agents/agent-profile.md for learning profile protocol.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
Usage
/profile Show current active profile
/profile list List all available profiles with summaries
/profile load <name> Load and apply a profile
/profile show <name> Show profile details without loading
/profile create <name> Create a new custom profile interactively
/profile diff <a> <b> Compare two profiles side by side
/profile validate Validate all profiles for schema compliance
/profile reset Reset to default profile
Instructions
You are the Session Profile Manager. Profiles control how /go, /forge, /ship, and all other commands behave. A misconfigured profile leads to wasted tokens, skipped gates, or unsafe autonomous execution. Your job is to ensure profiles are valid, applied correctly, and visible to the developer.
PHASE 1: PROFILE SELECTION
1.1 Locate Profiles
Scan for all profile files:
LOCATION: .claude/profiles/*.json
Expected built-in profiles:
├── default.json # Balanced: semi-auto + parallel
├── blitz.json # Speed: semi-auto + parallel + TDD
├── cautious.json # Oversight: manual + no parallel + verbose
└── autonomous.json # Full auto: autonomous + parallel + auto-commit
1.2 Validate Selection
When load <name> is invoked:
- Check
.claude/profiles/<name>.jsonexists - Parse JSON — reject if malformed
- Validate against profile schema (see below)
- Report any missing required fields
- If valid, proceed to PHASE 2
1.3 Profile Schema (Required Fields)
Every profile MUST contain these fields:
{
"name": "string (required) — unique profile identifier",
"description": "string (required) — human-readable purpose",
"mode": "string (required) — supervised|semi-auto|autonomous|manual",
"parallel": "boolean (required) — enable parallel story execution",
"tdd": "boolean (required) — enforce TDD mode for /coder",
"security_audit": "boolean (required) — run security audit per story",
"layer_check": "boolean (required) — run layer-check validation",
"memory_harvest": "boolean (required) — harvest knowledge after execution",
"auto_commit": "boolean (required) — auto-commit after each story",
"verbose": "boolean (required) — verbose output logging",
"token_budget": {
"max_per_story": "number (optional) — max tokens per story, default 50000",
"max_per_session": "number (optional) — max tokens per session, default 500000",
"warn_threshold": "number (optional) — warn at this percentage, default 80"
},
"agent_preferences": {
"anvil_tiers": "string (optional) — 't1,t2,t3,t4,t5,t6' or subset",
"retry_limit": "number (optional) — max retry attempts, default 3",
"escalation_mode": "string (optional) — immediate|batch|silent"
}
}
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 · 342 lines · 0 tokens per session scan A 517065cd9060
profile is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,758 tokens. 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 commands, from other repositories
act
Execute the implementation plan with TDD.
tailtest
Generate or update tests for $ARGUMENTS.
sessions
Generate implementation session prompts from a PRD or research doc.
deploy
Command "deploy" from PraveenJayaprakash-JP/repomemory, covering deployment workflow, 1. pre-deploy checks, 2. build verification, 3. environment validation and 4. deployment steps (platform detection).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.