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 keska-labs/enterprise-skills --skill add-skill-sourcegit clone --depth 1 https://github.com/keska-labs/enterprise-skillsWrote 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/keska-labs/enterprise-skills/add-skill-source)<a href="https://agentmods.dev/skills/keska-labs/enterprise-skills/add-skill-source"><img src="https://agentmods.dev/badge/skills/keska-labs/enterprise-skills/add-skill-source/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/keska-labs/enterprise-skills/add-skill-source"><img src="https://agentmods.dev/badge/skills/keska-labs/enterprise-skills/add-skill-source.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.00041 | $0.00846 |
| Opus 5 | $0.00020 | $0.00423 |
| Sonnet 5 | $0.00008 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
add-skill-source 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 12d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a skill source mode
Today the extension supports:
| Mode | Config | Listing | Content |
|---|---|---|---|
github-repo |
skillSync.sourceRepository |
RepoService.listSkillsInRepo |
RepoService.getSkillContent |
custom-registry |
skillSync.registryUrl |
RegistryService.listSkills |
RegistryService.getSkillContent |
SyncEngine.sync branches on configService.getSourceMode():
const skillIndex = sourceMode === "github-repo"
? await this.getGithubSkills()
: await this.registryService.listSkills();
const indexByName = new Map(skillIndex.map((skill) => [skill.name, skill]));
for (const skillName of optedInSkills) {
const meta = indexByName.get(skillName);
// ...
const content = sourceMode === "github-repo"
? await this.getGithubSkillContent(meta.path)
: await this.registryService.getSkillContent(meta.path);
Checklist for a new SourceMode
-
Types — Extend
SourceModeandSkillManagerState["sourceMode"]if the UI exposes the mode. -
Settings — Add enum value + any new keys under
contributes.configuration.propertiesinpackage.json(skillSync.sourceMode, plus URLs or IDs). -
ConfigService —
getSourceMode,setSourceMode, andisSourceConfigured()must know how to detect a valid configuration for the new mode. -
Service — Implement a class (or extend an existing one) that can produce
SkillMeta[]for the catalog andSkillContent(or package file fetches) compatible withSyncEngine:- For packages, set
skillType: "skill",pathto the package root identifier, and populateskillFileswith every file path the engine should download. - For single-file rules, use
skillType: "cursor-rule"and a stablepath/shaOrVersion.
- For packages, set
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.
- 12d ago First seen · 61 lines · 41 tokens per session scan A 3499992b1e3a
add-skill-source is a skill published in the GitHub repository keska-labs/enterprise-skills (7 stars, last pushed 23d ago), licensed MIT. It adds 41 tokens to every session and 846 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…