sdcorejs-skill-authoring

sdcorejs-skill-authoring is a skill for Codex from sdcorejs/sdcorejs-agent. It costs 50 tokens per session (1,368 once invoked), scanned A, original, MIT.

An internal authoring guide for maintaining the skill inventory and behavior of the sdcorejs-agent repository. It covers when to add a skill, how to update its source, and how to check changes.

In plain words
What is it for?
Use it when changing skill triggers, dispatch rules, shared contracts, evaluations, or the repository's skill list.
Why use it?
It keeps changes to agent skills based on observed behavior and prevents internal authoring rules from being shipped to user projects.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node authoring/evals/run-deterministic.mjs.

Good fit Use it when changing skill triggers, dispatch rules, shared contracts, evaluations, or the repository's skill list.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/sdcorejs/sdcorejs-agent
agentmods
npx agentmods add skills/sdcorejs/sdcorejs-agent/sdcorejs-skill-authoring

Made for: Codex.

Wrote 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.

agentmods badge for sdcorejs-skill-authoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-skill-authoring/github.svg)](https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-skill-authoring)
Your own site
<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-skill-authoring"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-skill-authoring/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.

agentmods 80×15 button for sdcorejs-skill-authoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-skill-authoring"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-skill-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,368 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01368
Opus 5.5 $0.00020 $0.00547
Sonnet 5.5 $0.00010 $0.00274
Haiku 4.5 $0.00005 $0.00137

Measured 25d ago against content hash acfc3ed08c8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sdcorejs-skill-authoring 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 25d 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.

authoring/skills/sdcorejs-skill-authoring/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SDCoreJS Skill Authoring

Author skill-pack changes from behavioral evidence, not from plausible-looking Markdown. This capability owns authoring discipline only; existing public skills retain their product, implementation, review, repair, and ship owners.

Scope boundary

  • Apply only while authoring the sdcorejs-agent repository or this skill pack.
  • Keep this capability under authoring/, outside public skills/**.
  • Never add it to harness manifests, generated mirrors, adapter inventories, the site catalog, package installation output, or target projects.
  • Edit canonical public sources first. Generate public mirrors only with the repository sync command; never hand-copy a mirror.
  • Do not treat a deadline, requester title, or batch request as approval to change dispatch contracts or inventory limits.

Read authoring/README.md, authoring/evals/scenarios.json, and authoring/evals/skill-authoring-contract.mjs before making an authoring decision.

New-skill decision gate

Default to an existing surface. A new public skill is justified only when all of these are evidenced:

  1. distinct user intent and trigger;
  2. distinct lifecycle;
  3. distinct artifact authority or execution boundary;
  4. no clean expression as an existing skill action, mode, or reference;
  5. positive and negative routing evidence;
  6. acceptable surface and complexity cost.

Otherwise choose exactly one owned fallback:

  • existing-skill-mode;
  • shared-reference;
  • executable-helper;
  • test-fixture;
  • documentation-only.

Call evaluateNewSkillDecision. It derives public names/count/hash and the routing-matrix hash from this repository; supplied count or free-form routing claims cannot replace them. Proposals are nonempty and cannot duplicate the inventory. Adding a trigger needs a canonical approved artifact resolved from the trusted loader and bound to actor, proposal scope, the current Git revision, and current inventory hash. A colocated JSON file and its caller-computed hash are not approval. The public count has ceiling 24; a boolean or owner instruction cannot override it.

Read the full file on GitHub · 146 lines

Files

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.

Changes

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.

  1. 25d ago Changed acfc3ed08c8e
  2. 2mo ago First seen · 146 lines · 50 tokens per session scan A 58d1309fc224

Subscribe to this mod's changes

sdcorejs-skill-authoring is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 50 tokens to every session and 1,368 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-08-31.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens