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 choose-fsharp-web-frameworkgit 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/choose-fsharp-web-framework)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/choose-fsharp-web-framework"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/choose-fsharp-web-framework/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/choose-fsharp-web-framework"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/choose-fsharp-web-framework.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.00051 | $0.00749 |
| Opus 5.5 | $0.00020 | $0.00300 |
| Sonnet 5.5 | $0.00010 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
choose-fsharp-web-framework 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Choose F# Web Framework
Choose the web surface before scaffolding. Keep the application's F# domain model, HTTP host, persistence, and deployment decision explicit instead of treating a framework DSL as the whole architecture.
Source Check
Inspect the repository and its locked packages first. When a current framework behavior matters, use its official documentation before generating code:
Selection
| Need | Default fit | Why |
|---|---|---|
| Small service using standard ASP.NET endpoint conventions | Minimal APIs | Least extra framework surface; keep idiomatic F# modules around the host. |
| Composable middleware-style functional handlers | Giraffe | HttpHandler composition over the ASP.NET Core pipeline. |
| Lightweight functional API or full-stack server toolkit | Falco | Direct routing and response helpers with ordinary ASP.NET Core integration. |
| Endpoint-routing / Minimal-API-shaped F# DSL | Oxpecker | F# endpoint handlers and middleware on ASP.NET Core Endpoint Routing. |
| Established convention-heavy F# MVC application | Saturn | Use only when its MVC/scaffolding shape is desired by the project. |
Do not select from popularity alone. Check existing package choices, team experience, endpoint style, HTML/view needs, authentication, hosting, and how much framework-specific API the project is willing to own.
Workflow
- Classify the application: API, HTML server app, webhook, internal tool, background worker with health endpoints, or full-stack application.
- Inspect its existing ASP.NET Core host, package versions, test harness, configuration, and deployment files.
- State the chosen framework and why the alternatives do not fit this project.
- Keep domain operations in F# modules independent of HTTP handlers.
- Use the matching framework skill for Giraffe, Falco, or Oxpecker. For Minimal
APIs use
dotnet:aspnet-core-service-workflow; for Saturn, inspect its local conventions and official documentation before making framework-specific edits. - Select the smallest useful test level and run
dotnet buildplus the relevantdotnet testcommand.
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 · 67 lines · 51 tokens per session scan A 54323cd5c16a
choose-fsharp-web-framework is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 749 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…