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/nerdai/llm-agents-from-scratch/create-issuenpx skills add nerdai/llm-agents-from-scratch --skill create-issuegit clone --depth 1 https://github.com/nerdai/llm-agents-from-scratchWrote 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/nerdai/llm-agents-from-scratch/create-issue)<a href="https://agentmods.dev/skills/nerdai/llm-agents-from-scratch/create-issue"><img src="https://agentmods.dev/badge/skills/nerdai/llm-agents-from-scratch/create-issue.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 | $0.00025 | $0.00665 |
| Opus 5 | $0.00013 | $0.00332 |
| Sonnet 5 | $0.00005 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
create-issue 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 5d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Issue
Repo and project
- Repo:
nerdai/llm-agents-from-scratch - Project:
#11(owner:nerdai)
Workflow
-
Before doing anything, confirm you have enough information. If any of the following are unclear, ask the user before proceeding:
- What is the issue title or topic?
- What kind of issue is it? (standard, book-diagram, or other)
- Which chapter is it scoped to, if any?
- Any specific labels to apply?
Do not create the issue until you have a clear title and kind.
-
Identify issue details from the user's request:
- Title — concise, action-oriented
- Body — see templates below based on kind
- Labels — from user request, or infer from kind
- Chapter label — add
Chapter Nlabel if the issue is scoped to a chapter
-
Create the issue:
gh issue create \ --repo nerdai/llm-agents-from-scratch \ --title "<title>" \ --body "<body>" \ --label "<label>" -
Add to project #11:
gh project item-add 11 --owner nerdai --url <issue-url> -
If the
Chapter Nlabel doesn't exist yet, create it first:gh label create "Chapter N" \ --repo nerdai/llm-agents-from-scratch \ --color 0075ca \ --description "Chapter N — <title>" -
Confirm with the issue URL.
Issue kinds
Standard issue
## Overview
<1-2 sentence summary of what needs to be done>
## Acceptance Criteria
- [ ] <criterion>
- [ ] <criterion>
## Related
<chapter, dependency, or context>
Book diagram
Title format: Diagram: <description>
Label: diagram (create if it doesn't exist)
## Overview
<What this diagram communicates and where it appears in the book>
## Chapter
Chapter N — <chapter title>
## Diagram type
<UML class diagram / sequence diagram / flowchart / table / other>
## Content to show
- <element>
- <element>
## Notes
<Any layout hints, style notes, or references>
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.
- 5d ago First seen · 115 lines · 25 tokens per session scan A 3e011c15b081
create-issue is a skill published in the GitHub repository nerdai/llm-agents-from-scratch (184 stars, last pushed 6d ago), licensed Apache-2.0. It adds 25 tokens to every session and 665 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-30.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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.
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…