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 dazz/kostja94-marketing-skills --skill howto-sectiongit clone --depth 1 https://github.com/dazz/kostja94-marketing-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/dazz/kostja94-marketing-skills/howto-section)<a href="https://agentmods.dev/skills/dazz/kostja94-marketing-skills/howto-section"><img src="https://agentmods.dev/badge/skills/dazz/kostja94-marketing-skills/howto-section/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/dazz/kostja94-marketing-skills/howto-section"><img src="https://agentmods.dev/badge/skills/dazz/kostja94-marketing-skills/howto-section.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.00194 | $0.03072 |
| Opus 5 | $0.00097 | $0.01536 |
| Sonnet 5 | $0.00039 | $0.00614 |
| Haiku 4.5 | $0.00019 | $0.00307 |
Grade A, and why
howto-section-generator 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 11d 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
100% identical to howto-section-generator — 0 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Components: HowTo Section
Guides HowTo as an in-page section: a block of ordered steps (and optional HowTo JSON-LD) embedded inside article, documentation, tool, or landing pages. Not a standalone page type—parent page structure and templates come from article-page-generator, docs-page-generator, tools-page-generator, landing-page-generator, etc. Distinct from FAQ (Q&A → FAQPage) and from full article body drafting alone (article-content). schema-markup remains the source for exhaustive Schema.org property rules and type-wide tables; this skill owns section-level placement, copy, HTML, and HowTo-vs-FAQ decisions.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
HowTo Section vs FAQ Section
| Dimension | HowTo section | FAQ section |
|---|---|---|
| Intent | User follows ordered steps to complete a task | User reads Q&A pairs for doubts |
| Structure | Steps (1→2→3), optional tools/time/supplies | Question → answer per item |
| Schema | HowTo (Schema.org) | FAQPage |
| UI | Often horizontal tabs for steps; or numbered list in flow | Often vertical accordion |
| Skill | howto-section-generator (this) | faq-page-generator |
Do not mark FAQ content as HowTo or vice versa; schema must match visible content.
Placement Within the Parent Page
This section is always part of a larger page. Typical positions:
| Location | When |
|---|---|
| After intro (and optional TL;DR / Key Takeaways) | Article: context first, then solution = steps |
| As the main middle of the page | Tutorial-heavy article where the HowTo block carries most of the value |
| After product/tool context | Tool or LP: short context → How to use steps → FAQ/CTA |
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.
- 11d ago First seen · 173 lines · 194 tokens per session scan A 841e721df7c6
howto-section-generator is a skill published in the GitHub repository dazz/kostja94-marketing-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 194 tokens to every session and 3,072 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to howto-section-generator, differing in 0 lines, and is treated as a copy.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…