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 skills/samibs/skillfoundry/gosmnpx skills add samibs/skillfoundry --skill gosmgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00013 | $0.00601 |
| Opus 5 | $0.00006 | $0.00300 |
| Sonnet 5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
gosm 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 3d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gosm - Go Semi-Auto Orchestrator
/gosm is a thin alias for /go --mode=semi-auto. It runs the full /go pipeline but auto-fixes routine issues and escalates only critical decisions to you. This is the recommended execution mode.
Persona: See agents/fixer-orchestrator.md for auto-remediation.
Reflection Protocol: See agents/_reflection-protocol.md.
Dispatch
/gosm [args] → /go --mode=semi-auto [args] with full argument passthrough. Every pipeline phase, Anvil gate, batch/context checkpoint, resume, and delivery audit is defined once in /go; /gosm only preselects the mode.
/gosm genesis/auth.md → /go --mode=semi-auto genesis/auth.md
/gosm --parallel → /go --mode=semi-auto --parallel
/gosm --tdd --parallel → /go --mode=semi-auto --tdd --parallel
/gosm --resume → /go --mode=semi-auto --resume
Extra flags: --resume (continue from saved state), --escalation-log (show deferred escalations).
What semi-auto mode adds
The one behavior semi-auto layers over /go: an auto-fix-vs-escalate decision on every gate finding. Deterministic, routine issues are fixed silently; anything needing human judgment is escalated.
| Category | Issue | Action |
|---|---|---|
| Tests | Missing unit tests / coverage < 80% | AUTO-FIX |
| Security | Missing standard headers (CSP, CSRF) | AUTO-FIX |
| Security | Hardcoded secret / auth-authz pattern choice | ESCALATE |
| Code | Dead code, duplication, banned patterns (TODO/FIXME) | AUTO-FIX |
| Docs | Missing API documentation | AUTO-FIX |
| Performance | N+1 query, missing index | AUTO-FIX |
| Performance | Caching strategy | ESCALATE |
| Architecture | Multiple valid approaches | ESCALATE |
| Business | Ambiguous requirement | ESCALATE |
| Database | Schema design choice | ESCALATE |
| API | Breaking change to consumers | ESCALATE |
On escalation, present: story, phase, issue type, context, options with trade-offs, and a recommendation — then wait for input. If the auto-fix rate falls below 70% for a run, recommend switching to /go (supervised) — most findings need human decisions, so semi-auto is buying little. Everything else — phases, gates, delivery audit — is /go's behavior unchanged.
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.
- 3d ago First seen · 50 lines · 13 tokens per session scan A 623365d0a6b9
gosm is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 601 once invoked, about $0.0001 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-30.
Other skills, from other repositories
ring:adopting-lib-commons-huma-wrapper
Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…
golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
go-idioms
Go stdlib, error wrapping, interfaces, goroutines, table-driven tests, gofumpt.
rust-skills
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros…
golang-development
You MUST activate this skill when working on Go projects.
first-plan-lens-go
Stack lens para projetos Go. Use durante Discovery quando go.mod for detectado. Extrai padrões de layout (cmd/internal/pkg), error handling, context.Context, concurrency, code generation, build tags.