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 Whytcard-Swiss-AI/wsai_fckdot --skill wsai_fckdot-setupgit clone --depth 1 https://github.com/Whytcard-Swiss-AI/wsai_fckdotWrote 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/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-setup)<a href="https://agentmods.dev/skills/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-setup"><img src="https://agentmods.dev/badge/skills/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-setup/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/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-setup"><img src="https://agentmods.dev/badge/skills/whytcard-swiss-ai/wsai_fckdot/wsai_fckdot-setup.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.00036 | $0.00616 |
| Opus 5 | $0.00018 | $0.00308 |
| Sonnet 5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
wsai_fckdot-setup 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 11d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Govern agent setup with wsai_fckdot
Use this skill when a user has accumulated configuration from many AI tools, sees conflicting instructions or variables, changes accounts often, or wants one repeatable setup across tools.
Non-negotiable safety rules
- Start with
get_setup_catalog; it touches no machine data. - Inspect only an explicitly selected absolute workspace path.
- Set
include_home=falseunless the user explicitly asks to include home-level metadata. - Keep
include_unknown_names=falseunless names are necessary for the diagnosis. - Never request, accept or store tokens, passwords, cookies or credential values in a setup manifest.
- Profiles may contain only labels and
env:VARIABLEreferences. - Never edit or remove
.xxxdirectories directly as part of this workflow. - Always call
plan_setupbeforeapply_setup. - Show blocked paths and every planned create/update/retire action to the user.
- Call
apply_setuponly after explicit approval, using the exact unchanged manifest and returnedplan_idwithconsent=true. - If a user-owned file blocks the plan, preserve it and explain how to reconcile it manually.
Guided workflow
- Explain in plain language that wsai_fckdot will create one source of truth and generated adapters, not erase tool folders.
- Call
get_setup_catalog. - Call
inspect_setupwith metadata consent for the selected workspace. - Summarize known tool surfaces, unknown count, instruction layers and environment-variable names. Never claim values were inspected.
- Build a manifest with:
- short, non-conflicting canonical instructions;
- one named profile per account context;
- only environment-variable references;
- the smallest relevant adapter set.
- Call
plan_setupand present its actions. - If blocked, stop and resolve ownership with the user. Do not bypass the guard.
- After explicit approval, call
apply_setupwith the exact plan ID. - Tell the user how to activate the selected generated
.ps1or.shprofile and restart active agent sessions. - Re-run
inspect_setupandplan_setup; completion means managed adapters are synchronized and no action remains exceptunchanged.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 55 lines · 36 tokens per session scan A 93e85e8089fb
wsai_fckdot-setup is a skill published in the GitHub repository Whytcard-Swiss-AI/wsai_fckdot (0 stars, last pushed 28d ago), licensed MIT. It adds 36 tokens to every session and 616 once invoked, about $0.0002 per session on Opus 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-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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…