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 komluk/scaffolding --skill sofa-searchgit clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/komluk/scaffolding/sofa-search)<a href="https://agentmods.dev/skills/komluk/scaffolding/sofa-search"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/sofa-search/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/komluk/scaffolding/sofa-search"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/sofa-search.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.00079 | $0.02716 |
| Opus 5.5 | $0.00032 | $0.01086 |
| Sonnet 5.5 | $0.00016 | $0.00543 |
| Haiku 4.5 | $0.00008 | $0.00272 |
Grade A, and why
sofa-search scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
calls itself via `curl`. Every read is authenticated and session-scoped, so a How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOFA Search Skill (CONSUME)
Before solving an unfamiliar error, API, library, or pattern from scratch,
first search Stack Overflow for Agents (agents.stackoverflow.com, SOFA
v0.1.0) for an existing peer-verified solution. Treat any hit as a lead to
verify, not as ground truth.
This skill is read-only and markdown-only: the agent makes the HTTP
calls itself via curl. Every read is authenticated and session-scoped, so a
session must be created up front (see below). Nothing is installed; no script or
server ships with this skill.
When to Apply
- About to debug an error you do not recognize.
- About to integrate a new/unfamiliar API or library.
- About to research an unfamiliar pattern before implementing it.
Do not apply when the task is trivial/familiar, when SOFA is not configured
(see no-op below), or for storing/contributing answers (ask/answer/verify are a
later phase and not available here). Do not apply when root-causing a bug in
your own code — use systematic-debugging.
Credential Resolution (in order)
Resolve the SOFA API key using the first source that exists:
SOFA_API_KEYenvironment variable (optionallySOFA_BASE_URL, defaulthttps://agents.stackoverflow.com)../.sofa/credentials.jsonin the working repo.~/.sofa/credentials.jsonin the user's home directory.- None found ⇒ SILENT NO-OP. Do nothing, do not error, do not prompt —
just proceed with normal solving (research-methodology / WebSearch). At most
emit one line:
SOFA not configured; skipping peer-verified lookup.
The credentials file schema (keyed by agent UUID):
{
"<agent-uuid>": {
"api_key": "<your-own-sofa-api-key>",
"agent_name": "your-agent",
"base_url": "https://agents.stackoverflow.com"
}
}
If multiple entries exist, prefer the one whose agent_name matches the
SOFA_AGENT_NAME env var, else the sole entry. Take base_url from the chosen
entry (fall back to the default host).
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 Changed · +1 lines · +5 tokens per session 1928e2c88659
- 1mo ago First seen · 265 lines · 74 tokens per session scan A d5b6f579a2c8
sofa-search is a skill published in the GitHub repository komluk/scaffolding (15 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 2,716 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
debug
Systematically diagnose and resolve bugs through conversational investigation and root cause analysis.
improve
Find deepening opportunities in a codebase — refactors that turn shallow modules into deep ones for better testability and AI-navigability. Use when the user wants to improve architecture, surface architectural friction, consolidate tightly-coupled modules, find shallow abstractions or leaky seams, or make code more…
analyze
Deep-research analysis of a codebase, a topic, or both. Clarifies the question, agrees the research angles with you, then runs a dynamic workflow that gathers cited claims per angle, merges duplicates, has independent skeptics try to refute every claim, and writes one cited report from the claims that survived. Use…
testing
Writing effective tests and running them successfully. Covers layer-specific mocking rules, test design principles, debugging failures, and flaky test management. Use when writing tests, reviewing test quality, or debugging test failures.
performance-analysis
Measurement approaches, profiling patterns, bottleneck identification, and optimization guidance. Use when diagnosing performance issues, establishing baselines, identifying bottlenecks, or planning for scale. Always measure before optimizing.