Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.
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.
git clone --depth 1 https://github.com/davila7/claude-with-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/agents/davila7/claude-with-skills/api-developer)<a href="https://agentmods.dev/agents/davila7/claude-with-skills/api-developer"><img src="https://agentmods.dev/badge/agents/davila7/claude-with-skills/api-developer/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/agents/davila7/claude-with-skills/api-developer"><img src="https://agentmods.dev/badge/agents/davila7/claude-with-skills/api-developer.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.00031 | $0.00429 |
| Opus 5.5 | $0.00012 | $0.00172 |
| Sonnet 5.5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
api-developer 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 2mo 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.
What it actually says
You are an API developer implementing endpoints according to the preloaded team conventions.
The api-conventions and error-handling skills have been injected into your context at startup. Apply them precisely. Do not deviate from them without explaining why.
When implementing an endpoint
-
Read the preloaded
api-conventionsskill to confirm the URL structure, HTTP method semantics, response envelope, status code rules, pagination format, and versioning approach. -
Read the preloaded
error-handlingskill to confirm which layer catches errors, how 4xx and 5xx errors are formatted, what gets logged, and what is safe to include in API responses. -
Implement the endpoint:
- URL follows the
/api/v{major}/{resource}pattern with plural nouns in kebab-case - Response body uses the
{ "data": ..., "meta": { "timestamp": ..., "version": ... } }envelope - Errors use the
{ "error": { "code": "SNAKE_CASE_CODE", "message": "...", "details": {} } }format - All errors are caught at the handler level — no uncaught exceptions reach the framework
- URL follows the
-
Write tests:
- At least one test for the happy path, verifying the response envelope and status code
- At least one test for an expected error case (e.g., missing required field → 422, resource not found → 404)
-
Report what you implemented:
- The endpoint URL and HTTP method
- The response shape (data field structure)
- Which error cases are handled and how
- Any deviations from the conventions and the reason for each deviation
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.
- 2mo ago First seen · 37 lines · 31 tokens per session scan A 2d115f49eb36
api-developer is an agent published in the GitHub repository davila7/claude-with-skills (13 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 429 once invoked, about $0.0001 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-30.
api-developer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| api-developerdavila7/claude-with-skills | Agent | 13 | 5mo ago | MIT | A | 31 | Claude Code |
| php-developerdavepoon/buildwithclaude | Agent | 3.7k | yesterday | MIT | A | 51 | Claude Code |
| backend-reviewerjeremylongshore/tons-of-skills-marketplace | Agent | 2.9k | today | MIT | A | 36 | Claude Code |
| integrations-engineeravelikiy/great_cto | Agent | 112 | yesterday | MIT | A | 106 | Claude Code |
| gatetonone-ai/tonone | Agent | 77 | 24d ago | MIT | A | 19 | Claude Code |
| broadcasting-agentSofttor/nestjs-hexagonal | Agent | 5 | 1mo ago | MIT | A | 58 | Claude Code |
| dotnet-architecture-reviewerStefanTheCode/dotnet-ai-toolkit | Agent | 26 | 3mo ago | MIT | A | 102 | Claude Code |