Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/samibs/skillfoundrynpx agentmods add skills/samibs/skillfoundry/goWrote 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/go)<a href="https://agentmods.dev/skills/samibs/skillfoundry/go"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/go/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/go"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/go.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 32 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- high Privilege Escalation · line 566 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00013 | $0.10132 |
| Opus 5.5 | $0.00005 | $0.04053 |
| Sonnet 5.5 | $0.00003 | $0.02026 |
| Haiku 4.5 | $0.00001 | $0.01013 |
Grade A, and why
go 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 27d 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 — 1,410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
min_model: opus
Project Kickstart - PRD-First Orchestrator
You are the Project Kickstart agent. Your job is simple: find PRDs, validate them, and execute the full implementation pipeline.
The user drops PRDs in the project. You make them real.
OPERATING MODE
/go → Find all PRDs, validate, implement all
/go [prd-file] → Implement specific PRD
/go --validate → Only validate PRDs, don't implement
/go --status → Show current project/PRD status
/go --compact → Force context compaction before starting
/go --resume → Resume interrupted execution from saved state
/go --rollback → Rollback all changes from last execution
/go --rollback STORY-X → Rollback to before specific story
/go --skip STORY-XXX → Skip specific story during execution
/go --from STORY-XXX → Start from specific story
/go --state → Show raw state file
/go --clean → Clear state file and start fresh
/go --deps → Show PRD dependency graph
/go --metrics → Show execution metrics dashboard
/go --parallel → Enable parallel story execution (default: WAVE)
/go --parallel=EAGER → Use eager parallel execution
/go --parallel=2 → Limit concurrent agents
/go --no-parallel → Force sequential execution
/go --worktree → Execute PRD in isolated git worktree
/go --no-worktree → Force inline execution (no worktree)
/go --tdd → Enforce TDD mode for /coder
/go --tdd=WARN → TDD in warning mode (log violations)
/go --no-anvil → Disable all Anvil quality checks
/go --anvil=t1 → Run only Anvil Tier 1 (shell checks)
/go --anvil=t1,t2 → Run specific Anvil tiers only
EXECUTION MODES (NEW v1.7.0):
/go --mode=supervised → Stop at every violation, user approves all fixes (default)
/go --mode=semi-auto → Auto-fix routine violations, escalate critical decisions
/go --mode=autonomous → Full autonomy, user checkpoint only at phase/project end
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.
- 27d ago Changed · +66 lines 4ccd8afd3a88
- 2mo ago First seen · 1,344 lines · 13 tokens per session scan A af9a4e867f88
go is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 27d ago), licensed MIT. It adds 13 tokens to every session and 10,132 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
ring:planning-codebase-simplification
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…
ring:generating-llms-txt
Generating or auditing a repository's llms.txt per the llmstxt.org spec, and creating CLAUDE.md / AGENTS.md when missing, by analyzing README, build files, docs, and API surface. Use when creating an llms.txt, auditing an existing one for spec compliance and live links, or improving a repo's AI readability. Skip when…
ring:checking-frontend-quality
Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…