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 gosmgit 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/gosm)<a href="https://agentmods.dev/skills/samibs/skillfoundry/gosm"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/gosm/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/gosm"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/gosm.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.00013 | $0.00601 |
| Opus 5.5 | $0.00005 | $0.00240 |
| Sonnet 5.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 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.
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.
- 1mo 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 15d ago), licensed MIT. It adds 13 tokens to every session and 601 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:verifying-code
Verifying a Go project: runs every quality check (lint, vet, imports, format, docs, unit, integration, E2E) and returns a single MERGEREADY or NEEDSFIX verdict. Report-only: never fixes anything. Use for a quick pre-merge or pre-PR check outside a full dev-cycle. Skip when not a Go project, when you want a single…
golang-pro
Go development expertise. Concurrency patterns, error handling, project structure, and performance optimization. Use when building Go services, CLIs, or systems tools.
golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
ring:applying-licenses
Applying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no…
content-audit
Content file quality audit across 8 dimensions (CC1-CC8): encoding artifacts (NBSP, mojibake, zero-width), markdown syntax (broken italic, orphan backslash), CMS migration artifacts (Joomla/WordPress/PHP), frontmatter quality, image integrity, link integrity with anchor validation, content completeness, and…