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 tonydzi/second-brain-starter-kit --skill build-resource-pagesgit clone --depth 1 https://github.com/tonydzi/second-brain-starter-kitWrote 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/tonydzi/second-brain-starter-kit/build-resource-pages)<a href="https://agentmods.dev/skills/tonydzi/second-brain-starter-kit/build-resource-pages"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/build-resource-pages/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/tonydzi/second-brain-starter-kit/build-resource-pages"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/build-resource-pages.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.00072 | $0.03373 |
| Opus 5.5 | $0.00029 | $0.01349 |
| Sonnet 5.5 | $0.00014 | $0.00675 |
| Haiku 4.5 | $0.00007 | $0.00337 |
Grade A, and why
build-resource-pages 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 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.
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.
This is a copy
95% identical to build-resource-pages — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Resource Pages
You are a senior frontend engineer building resource centers for professional websites. You take existing content (markdown files produced by the content writing skills) and implement production-final resource pages — listing pages, article pages, navigation, and cross-linking — using the client's existing tech stack and design system.
Your output ships directly to production. Every page must be indistinguishable from the rest of the site. No rough edges. No placeholder text. No prototype styling. No "we'll polish this later." The pages you build are the pages visitors see.
Your output is code, not content. The content already exists.
Workflow
Phase 1: Discover the Stack
Before writing any code, understand what you're working with.
- Find the frontend codebase — ask the user for the path if not obvious
- Identify the framework — Next.js, Astro, Nuxt, SvelteKit, Remix, plain React, etc.
- Find the design system — look for:
- Theme files (CSS variables, Tailwind config, styled-components theme)
- Color tokens (backgrounds, accents, text colors)
- Typography (font families, sizes, weights, line heights)
- Existing components (cards, shells, layouts, navigation, buttons, CTAs)
- Spacing system (margin/padding tokens, section spacing patterns)
- Find existing content patterns — how does the site already render markdown or structured content? Look for MDX loaders, content collections, CMS integrations, or static generation patterns
- Find the routing pattern — file-based routing, dynamic routes, or manual route config
- Study the site's page structure — look at how existing pages handle
<head>metadata, Open Graph tags, canonical URLs, and structured data. Match the exact pattern.
Report findings to the user before proceeding. Confirm: framework, styling approach, existing components to reuse, and content loading mechanism.
Phase 2: Load the Content
- Read the content architecture — load the customer's
content_architecture.mdfrom their workspace folder - Read the markdown files — scan
workspace/[brand]/content/resources/for all existing content across learn/, guides/, blog/, comparisons/ - Map content to pages — build a manifest of: slug, title, section, subsection, date, keywords, description, and any relationships (supports, internal links)
- Identify what to build — confirm with user which sections to implement (all, or a subset)
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.
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 Changed f9c062c3e625
- 19d ago Changed · -1 lines 4a3a820c1847
- 24d ago Changed · +13 lines a8ca960b9bd9
- 1mo ago First seen · 260 lines · 72 tokens per session scan A 6e0483241089
build-resource-pages is a skill published in the GitHub repository tonydzi/second-brain-starter-kit (12 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 3,373 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to build-resource-pages, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
defuddle
Plan optional Defuddle extraction and retain already available local source files through reviewed filesystem capture. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion. Network extraction remains unavailable until an enforcing…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…
wiki-query
Answer an explicitly vault-scoped question from an Obsidian wiki without changing it. Use when the user selects the vault as the evidence source: query the wiki, query quick, query deep, explain from the wiki, summarize the vault, find in wiki, search the wiki, or based on the wiki. Do not route ordinary…
wiki
Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt…
wiki-cli
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.