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 darthzen/fossa-mcp --skill fossa-api-auditgit clone --depth 1 https://github.com/darthzen/fossa-mcpWrote 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/darthzen/fossa-mcp/fossa-api-audit)<a href="https://agentmods.dev/skills/darthzen/fossa-mcp/fossa-api-audit"><img src="https://agentmods.dev/badge/skills/darthzen/fossa-mcp/fossa-api-audit.svg" alt="Measured on agentmods" 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.00099 | $0.03876 |
| Opus 5 | $0.00049 | $0.01938 |
| Sonnet 5 | $0.00020 | $0.00775 |
| Haiku 4.5 | $0.00010 | $0.00388 |
Grade A, and why
fossa-api-audit 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 8d 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.
curl -s -H "Authorization: Bearer $FOSSA_API_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fossa-api-audit
Parse the vendored spec, derive the registered tool surface from the code as it sits on disk, cross them into a coverage matrix, exercise every read endpoint against the live API, run the refusal tests to prove the write gate holds, and report the gaps.
Why this workflow exists: three surfaces drift independently. The vendored
spec (spec/fossa-openapi.json) is regenerated from FOSSA's published swagger
and grows on FOSSA's schedule; the registered tool list changes per branch —
this repo has had 9 tools on one branch and 13 on another at the same time,
with tool modules that exist but are not imported; and the live API answers for
what actually works today, for this org, with this token. An audit that
hardcodes any of the three answers a question nobody asked.
The honest framing, stated up front and never dropped: "live-verified"
means one successful call, from one org, at one moment. And the spec cannot
always be failed against: some GET operations give you nothing to compare a
200 against — at 4.34.55 that is 4 of 157, counting the 3 that document no 200
response at all plus GET /projects/{locator} (the known worst case), whose
200 schema is an object with zero properties — so a live response full of
fields the spec never mentions is
a spec gap to report, not a server bug to flag. Keep the two verdicts
separate everywhere they appear.
Run from the repo root. Results are branch-specific — name the branch
(git branch --show-current) in the report, first line.
1. Enumerate the documented surface
Confirm the spec exists before anything else. It lives at
spec/fossa-openapi.json on the branches where this skill is used
(api-parity, security-policy-writes) but not on every branch — if the file
is missing, read it out of git without switching branches, and point SPEC
at the copy — every snippet in this skill reads $SPEC, which defaults to the
checked-in path:
git show api-parity:spec/fossa-openapi.json > "$TMPDIR/fossa-openapi.json"
export SPEC="$TMPDIR/fossa-openapi.json"
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.
- 8d ago First seen · 308 lines · 99 tokens per session scan A d42ac879ca88
fossa-api-audit is a skill published in the GitHub repository darthzen/fossa-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 99 tokens to every session and 3,876 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…