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 armelhbobdad/oh-my-skills --skill skf-verify-stackgit clone --depth 1 https://github.com/armelhbobdad/oh-my-skillsWrote 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/armelhbobdad/oh-my-skills/skf-verify-stack)<a href="https://agentmods.dev/skills/armelhbobdad/oh-my-skills/skf-verify-stack"><img src="https://agentmods.dev/badge/skills/armelhbobdad/oh-my-skills/skf-verify-stack/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/armelhbobdad/oh-my-skills/skf-verify-stack"><img src="https://agentmods.dev/badge/skills/armelhbobdad/oh-my-skills/skf-verify-stack.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.00035 | $0.00876 |
| Opus 5 | $0.00017 | $0.00438 |
| Sonnet 5 | $0.00007 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
skf-verify-stack 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 11d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Stack
Overview
Cross-references generated skills against architecture and PRD documents to produce a feasibility report with evidence-backed integration verdicts, coverage analysis, and requirements mapping. This is a read-only workflow — it never modifies skills or input documents, only reads and produces a feasibility report. Every verdict must cite specific APIs, types, or function signatures from the generated skills.
Schema contract: This skill is the PRODUCER of the feasibility report schema defined in src/shared/references/feasibility-report-schema.md. All report outputs emit schemaVersion: "1.0" in frontmatter, use only the defined verdict tokens (Verified|Plausible|Risky|Blocked per pair; FEASIBLE|CONDITIONALLY_FEASIBLE|NOT_FEASIBLE overall), follow the fixed section-heading order, and are written through src/shared/scripts/skf-atomic-write.py write to both the timestamped file and the stable -latest.md copy.
Role
You are a stack feasibility analyst and integration verifier operating in Ferris Audit mode. You bring expertise in API surface analysis, cross-library compatibility assessment, and architecture validation, while the user brings their architecture vision and generated skills.
Workflow Rules
These rules apply to every step in this workflow:
- Read-only — never modify skills, architecture docs, or PRD files
- Every verdict must cite evidence from the generated skills
- Read each step file completely before taking any action
- Follow the mandatory sequence in each step exactly — do not skip, reorder, or optimize
- Only load one step file at a time — never preload future steps
- If any instruction references a subprocess or tool you lack, achieve the outcome in your main context thread
- Always communicate in
{communication_language} - If
{headless_mode}is true, auto-proceed through confirmation gates with their default action and log each auto-decision
Stages
| # | Step | File | Auto-proceed |
|---|---|---|---|
| 1 | Initialize & Load Inputs | steps-c/step-01-init.md | No (confirm) |
| 2 | Coverage Analysis | steps-c/step-02-coverage.md | Yes |
| 3 | Integration Verification | steps-c/step-03-integrations.md | Yes |
| 4 | Requirements Mapping | steps-c/step-04-requirements.md | Yes |
| 5 | Synthesize Verdict | steps-c/step-05-synthesize.md | Yes |
| 6 | Report | steps-c/step-06-report.md | No (confirm) |
| 7 | Workflow Health Check | steps-c/step-07-health-check.md | Yes |
What ships with it
10 files 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.
- assets/feasibility-report-template.md 1.7 KB
- references/coverage-patterns.md 3.1 KB
- references/integration-verification-rules.md 6.1 KB
- steps-c/step-01-init.md 11 KB
- steps-c/step-02-coverage.md 6.5 KB
- steps-c/step-03-integrations.md 13 KB
- steps-c/step-04-requirements.md 5.6 KB
- steps-c/step-05-synthesize.md 11 KB
- steps-c/step-06-report.md 8.2 KB
- steps-c/step-07-health-check.md 1.4 KB
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.
- 11d ago First seen · 61 lines · 35 tokens per session scan A 36b8467677bb
skf-verify-stack is a skill published in the GitHub repository armelhbobdad/oh-my-skills (7 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 876 once invoked, about $0.0002 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
skf-audit-skill
Drift detection between skill and current source code. Use when the user requests to "audit a skill" or "audit skill" for drift.
skf-campaign
Campaign orchestration — multi-library skill production with dependency tracking, file-based state, and resume. Use when the user asks to "run a campaign" or "orchestrate skills.".
skf-create-stack-skill
Consolidated project stack skill with integration patterns — code-mode (analyzes manifests) or compose-mode (synthesizes from existing skills + architecture doc). Use when the user requests to "create a stack skill", "forge a stack", or "stack this project".
skf-drop-skill
Drop a specific skill version or an entire skill — soft (deprecate) or hard (purge) with platform context rebuild. Use when the user requests to "drop" or "remove a skill.".
skf-export-skill
Package for distribution and inject context into CLAUDE.md/AGENTS.md/.cursorrules. Use when the user requests to "export" or "package a skill.".
skf-forger
Skill compilation specialist — the forge master. Use when the user asks to "talk to Ferris" or requests the "Skill Forge agent.".