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 Notysoty/openagentskills --skill sdk-quickstart-writergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/sdk-quickstart-writer)<a href="https://agentmods.dev/skills/notysoty/openagentskills/sdk-quickstart-writer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/sdk-quickstart-writer/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/notysoty/openagentskills/sdk-quickstart-writer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/sdk-quickstart-writer.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.00023 | $0.01750 |
| Opus 5 | $0.00012 | $0.00875 |
| Sonnet 5 | $0.00005 | $0.00350 |
| Haiku 4.5 | $0.00002 | $0.00175 |
Grade A, and why
SDK Quickstart Writer 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 9d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDK Quickstart Writer
What this skill does
This skill writes a concise, copy-paste-ready quickstart guide for any SDK or library. It produces a document that gets a developer from zero to their first working API call or feature in under 10 minutes — covering installation, setup, authentication, and a complete working example. The output follows the "get it working first, explain later" philosophy.
Use this when releasing a new SDK, when existing documentation is too verbose or scattered, or when onboarding developers who need a working example before reading the full API reference.
How to use
Claude Code / Cline
Copy this file to .agents/skills/sdk-quickstart-writer/SKILL.md in your project root.
Then ask:
- "Use the SDK Quickstart Writer skill to write a quickstart for our Node.js SDK."
- "Write a quickstart guide for developers integrating our REST API using the SDK Quickstart Writer skill."
Provide:
- The SDK name and language(s)
- Installation command
- Required credentials or API keys
- The most common or important first use case
- Any code samples you already have
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Provide SDK details and any existing code.
Codex
Provide the SDK name, the package name, authentication method, and a description of the primary use case. Ask Codex to follow the instructions below.
The Prompt / Instructions for the Agent
When asked to write an SDK quickstart, follow these steps:
Step 1 — Understand the SDK
Before writing, confirm you understand:
- Language / runtime: Node.js, Python, Go, browser JS, etc.
- Package name: What do developers install?
- Authentication: API key in header? OAuth? Client ID + secret?
- Primary use case: What's the first thing 80% of developers want to do?
- Base URL / environment: Any staging vs production distinction?
If this information isn't provided, ask before writing.
Step 2 — Structure the quickstart
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.
- 9d ago First seen · 215 lines · 23 tokens per session scan A d12e8ebd834d
SDK Quickstart Writer is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 25d ago), licensed MIT. It adds 23 tokens to every session and 1,750 once invoked, about $0.0001 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
onboarding-index
Discover CEP-managed content already present in a target repo (What/How layer docs, compiled guidelines, context packages, decision ledger) via existence checks against layout-slots-registry.yaml-resolved paths, then write one canonical root AGENTS.md onboarding index plus thin per-tool pointer stubs…
autoscaffold-content
Generate real starter content for a project's What-L2 (requirements) and How-L2 (architecture/conventions) CEP layers once ult-repo-layout has resolved their paths but found them empty — an honest, minimal, YAML-frontmatter-first overview document per layer for small/single targets, or graphify-informed per-module…
explain-codebase
Drop into any repo and generate a structured architecture overview. Maps the codebase, identifies entry points, frameworks, and dependencies — then produces a "start here" guide for new contributors.
pipefy-toolkit-setup
Guide a first-time user through Pipefy AI toolkit setup (Cursor Marketplace plugin, hosted MCP, local install.sh, or Claude Code plugin). Use when the user asks to install Pipefy MCP, connect Claude/Cursor to Pipefy, run /pipefy:install, or set up mcp.pipefy.com. Do not use for day-to-day Pipefy workflows after MCP is…
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
extract-source-sample
Given the path to a finished content-goose ad-run folder, extract everything that defines that ad — recipe shot list, VO script, characters, voices, world, atom-skills, master mp4 — and emit a source-sample.json in the exact shape the upload-ad-sample skill writes to the Goose Ads library. Also links every character…