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 agentmods add skills/codebygarv/ai-skills/sdk-getting-started-writernpx skills add codebygarv/Ai-skills --skill sdk-getting-started-writergit clone --depth 1 https://github.com/codebygarv/Ai-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/codebygarv/ai-skills/sdk-getting-started-writer)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/sdk-getting-started-writer"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/sdk-getting-started-writer.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.00033 | $0.00355 |
| Opus 5 | $0.00016 | $0.00178 |
| Sonnet 5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
sdk-getting-started-writer 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 6d 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.
description: Crafts developer quickstart guides, language SDK installation snippets, and copy-pasteable curl/Python/TypeScript samples. What it actually says
Purpose
Write developer-first "Getting Started" guides, SDK quickstarts, and interactive code snippets that enable engineers to make their first successful API call in under 3 minutes.
When to Use
- Launching a public API, developer SDK, or open-source library.
- High developer drop-off between creating an API key and making their first request.
- Writing documentation for multi-language client libraries (Node, Python, Go, cURL).
What to Analyze
- Time-to-First-Hello-World: Minimize steps between package install and first successful response.
- Prerequisites & API Key Setup: Clear instructions on environment variables (
export API_KEY=...). - Multi-Language Tabbed Snippets: Provide identical minimal examples in cURL, TypeScript, Python, and Go.
- Copy-Pasteable Completeness: Snippets must be 100% executable without missing imports or placeholder pseudo-code.
- Immediate Next Steps: Direct links to full API reference, webhook setup, and error code tables.
Output Format
- Quickstart Guide Markdown: 3-step guide: Install $ ightarrow$ Configure $ ightarrow$ First Request.
- Multi-Language Code Blocks: Tabbed cURL, Node.js, and Python working code.
- Expected JSON Response: Actual payload returned on success.
Avoid
- Hiding package install commands behind long introductory marketing paragraphs.
- Using un-runnable snippet fragments that omit imports or authentication headers.
What ships with it
2 files 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.
- 6d ago First seen · 34 lines · 33 tokens per session scan A 81abbdd1d267
sdk-getting-started-writer is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 17d ago), licensed MIT. It adds 33 tokens to every session and 355 once invoked, about $0.0002 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-30.
Other skills, from other repositories
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…
git-commit
Conventional Commits format for git commits and PR/MR titles. Type prefixes, scope rules, breaking change syntax, and commit message structure. Use when committing changes, writing commit messages, creating PR/MR titles, or formatting squash merge messages. Not for PR workflows (git-pr), CI/CD status (git-ci), or git…