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 quickgit 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/quick)<a href="https://agentmods.dev/skills/samibs/skillfoundry/quick"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/quick/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/samibs/skillfoundry/quick"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/quick.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00008 | $0.01314 |
| Opus 5.5 | $0.00003 | $0.00526 |
| Sonnet 5.5 | $0.00002 | $0.00263 |
| Haiku 4.5 | $0.00001 | $0.00131 |
Grade A, and why
quick scanned grade A 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
"child_process.exec(" # shell injection surface How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/quick — Lightweight Feature Workflow
Role: Minimal-ceremony feature workflow for solo developers and small changes. Implement → test → commit. No PRD required, no full pipeline overhead.
Usage
/quick "description" Implement, test, and commit a small feature
/quick "description" --challenge Add evaluator challenge (optional)
/quick "description" --no-commit Implement and test, skip commit
When to use
- Solo developer, informal feature request
- Small improvements (a flag, a config option, a new utility function)
- Prototyping before formalizing into a PRD
- Dark mode toggle, UI tweaks, non-critical additions
When NOT to use
- Production auth, payments, security-critical features → use
/feature - Multi-story features → use
/forge - When you need the full evaluator + docs pipeline → use
/feature
The Pipeline
/quick "add dark mode toggle to settings page"
STEP 1: IMPLEMENT Coder builds it (TDD when test scope is clear)
STEP 2: TESTLOOP Tests run, fixes loop until green (max 3 iterations)
STEP 3: COMMIT Scoped commit [ADVISORY if no shell]
Optional (--challenge flag only):
STEP 2.5: CHALLENGE Evaluator grades. Fix brief loops back to coder.
No shadow tester. No Anvil gates. No layer-check. No docs stage (code-level comments only). No security audit.
Behavior
Step 1: Implement
Coder reads the description and implements:
- If test scope is obvious (function, endpoint, component) → TDD: test first
- If test scope is unclear (UI tweak, config change) → implement then test
- Banned patterns still apply (no TODO, STUB, hardcoded secrets)
- No formal story scaffolding required
Step 2: TestLoop
Run /testloop with reduced settings:
/testloop --max 3 [auto-detected scope]
Max 3 iterations (vs. 5 in full /feature). If not converging after 3, report failures and stop — no further auto-fix. User decides next action.
Step 2.5: Challenge (optional, --challenge flag only)
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 · 187 lines · 8 tokens per session scan A 6ed87a518800
quick is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 19d ago), licensed MIT. It adds 8 tokens to every session and 1,314 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
gate
MANDATORY before every commit and push. All gates must pass — Gates 1–3 always run; Gates 4 (Docker) and 5 (Cloud) run only when applicable. Do NOT proceed if any gate fails — fix the issue first.
wrap-up-branch
Finish a feature branch: add missing tests, review and fix the code, align docs, then merge only after explicit confirmation.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.