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 commands/vaquarkhan/fullstack-development-agent-skills/specgit clone --depth 1 https://github.com/vaquarkhan/Fullstack-development-agent-skillsWhat 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.00000 | $0.00034 |
| Opus 5 | $0.00000 | $0.00017 |
| Sonnet 5 | $0.00000 | $0.00007 |
| Haiku 4.5 | $0.00000 | $0.00003 |
Grade A, and why
spec 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.
What it actually says
/spec
Use skills/fullstack-product-specification/SKILL.md to define business outcome, UI states, API contract, and risk boundaries before implementation.
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 · 4 lines · 0 tokens per session scan A 70460bbd4a6d
spec is a command published in the GitHub repository vaquarkhan/Fullstack-development-agent-skills (2 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 34 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-08-31.
Other commands, from other repositories
gh-issue-plan
This command provides guidance for both automated and manual GitHub issue workflows.
migrate-example
Migra un ejemplo de Web Worker al dominio neutral y lo renderiza en los 5 themes (pipeline punta a punta con loop de design-review).
Review Code Structure
Audit class responsibilities, package boundaries, duplication, and rule compliance across Issues.
Fix Sonar Issues
Run local static analysis and fix findings with conservative, behavior-preserving changes.
epic-plan
Run /epic-plan — see .claude/commands/epic-plan.md for the authoritative spec.
repo-orch-status
Show at-a-glance status of the repo-orchestrator workspace: registered repos, last index timestamps, graph availability, userEdited flags, and Agent Teams enablement.