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 gaelic-ghost/socket --skill build-oxpecker-web-appgit clone --depth 1 https://github.com/gaelic-ghost/socketWrote 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/gaelic-ghost/socket/build-oxpecker-web-app)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/build-oxpecker-web-app"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/build-oxpecker-web-app/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/gaelic-ghost/socket/build-oxpecker-web-app"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/build-oxpecker-web-app.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.00044 | $0.00478 |
| Opus 5.5 | $0.00018 | $0.00191 |
| Sonnet 5.5 | $0.00009 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
build-oxpecker-web-app 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Oxpecker Web App
Use Oxpecker's endpoint-routing model deliberately. Its F# DSL sits on ASP.NET Core Endpoint Routing, so native endpoint metadata and middleware behavior remain part of the application contract.
Source Check
Inspect the existing host, endpoints, middleware, project references, tests, and configuration. Use the Oxpecker documentation and ASP.NET Core routing documentation when local evidence does not answer the question.
Workflow
- Confirm Oxpecker is selected through
dotnet:choose-fsharp-web-framework. - Model one endpoint as an
EndpointHandler: validate or bind input, invoke a focused domain operation, and produce the response. - Use
EndpointMiddlewarefor a reusable pipeline concern with an explicit before/after or short-circuit behavior. Do not use it as a generic service locator or business-rule container. - Keep route patterns, HTTP methods, authorization requirements, tags, and other endpoint metadata co-located enough to review as one API contract.
- Continue using ASP.NET Core for host configuration, authentication, authorization, logging, and cross-cutting middleware. Preserve its pipeline ordering when introducing Oxpecker endpoints.
- Test domain behavior independently and endpoint behavior for routing, binding, status, metadata, authorization, and serialized response contracts.
Validation
Use the smallest project-level validation available, normally:
dotnet build <web-project.fsproj>
dotnet test <test-project.fsproj>
Boundaries
- Keep
.fsprojfile ordering explicit and preserveTaskboundaries at theHttpContextedge. - Do not assume Giraffe handlers or middleware map mechanically to Oxpecker; migrate only with an explicit route and test-contract review.
- Use the official Azure Skills plugin for Azure architecture, provisioning, diagnostics, and deployment decisions.
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 · 52 lines · 44 tokens per session scan A 26c3c5e86433
build-oxpecker-web-app is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 478 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
data-engineering
Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone…
api-design
Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.
architecture
Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.
api-design-document
Design a production-ready API specification aligned with OpenAPI 3.1 standards. Covers resource modeling, endpoint design, request/response contracts, authentication, versioning strategy, error handling, rate limiting, and pagination. Use when designing a new REST, GraphQL, or event-driven API.
contracts
Team baseline for external-interface contract artifacts: OpenAPI, JSON Schema, AsyncAPI, .proto, and GraphQL SDL, with spectral, ajv, buf, and graphql-inspector validation. Nudges devs toward contract-first artifacts; never writes them and never scaffolds a contracts/ directory. Auto-triggers for what contract should…
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…