Strands Agents is an open-source SDK for building and running AI agents in Python and TypeScript. Developers use it to create agents with model providers, tools, lifecycle controls, memory, sessions, streaming, tracing, and evaluations, and the catalogue includes add-ons for its agent-building workflow.
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/strands-agents/harness-sdk/docs-writernpx skills add strands-agents/harness-sdk --skill docs-writergit clone --depth 1 https://github.com/strands-agents/harness-sdkWrote 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/strands-agents/harness-sdk/docs-writer)<a href="https://agentmods.dev/skills/strands-agents/harness-sdk/docs-writer"><img src="https://agentmods.dev/badge/skills/strands-agents/harness-sdk/docs-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 | $0.00074 | $0.01728 |
| Opus 5 | $0.00037 | $0.00864 |
| Sonnet 5 | $0.00015 | $0.00346 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
docs-writer 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writer
Draft or rewrite Strands Agents documentation following the five-layer voice stack.
Inputs
- Content type: tutorial, howto, reference, explanation, blog (required)
- Topic: What this page covers (required)
- Target file: Path in docs repo where this will live (if known)
- Existing content: Current page to rewrite (if rewriting)
- Context (optional): Community signals, GitHub issues, or positioning themes motivating this work
Process
Step 1: Load voice context
Read these files before writing anything:
../../references/voice-guide.md(the full voice stack)../../references/terminology.md(canonical terms)
If rewriting, read the current published page as a baseline.
Step 2: Outline
Produce an outline where each item is the question that section answers.
- Tutorial: step-by-step journey toward a working result
- How-to: prerequisites, steps, expected result
- Reference: API surface (classes, methods, parameters)
- Explanation: problem, design choice, tradeoffs, implications
Each section answers one question. No mixed-type sections. Review for scope creep.
Step 3: Draft
Write each section following the outline.
- First sentence of every section describes the developer's goal (framing layer)
- Use the tone appropriate for this content type (register layer)
- Code examples: runnable with real Strands imports and realistic values
- For agent responses, label non-deterministic output following the patterns in
voice-guide.mdunder "Documenting non-deterministic behavior" (typical output as a comment under the code; capability language for tool selection). - Comments explain intent, not mechanics
- One concept per code block
- Match snippet length to the complexity of what's being demonstrated. Bias toward brevity. If setup machinery dwarfs the feature being shown, the snippet is overweight.
- Snippets must be copy-paste-runnable: imports present, variables defined, no missing context.
- Prefer prose over a snippet for trivial API surface. A single property, a single method call, or a one-line config change is often clearer as inline backtick code in a sentence than as a dedicated code block. Reach for a snippet when the shape, ordering, or interaction between calls carries the lesson.
- Diagrams use
```mermaidfences (flowchart, sequence, etc.). Never use ASCII art or box-drawing characters for diagrams. The site renders mermaid natively.
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 · 144 lines · 74 tokens per session scan A ed754d1219d9
docs-writer is a skill published in the GitHub repository strands-agents/harness-sdk (7,155 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 1,728 once invoked, about $0.0004 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
returns-policy
Answer return, refund, and warranty questions for electronics. Use when the user mentions returns, refunds, RMAs, warranty coverage, damaged items, or opened packaging.
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
docs-audit
Assess a published or in-progress documentation page for quality, accuracy, and voice compliance. Use before rewriting a page, during periodic health checks, when community signals point to confusion, or when comparing against competitor docs. Also triggers on "audit this page", "assess the docs", "what's wrong with…
docs-reviewer
Review documentation drafts for voice consistency, structure, and terminology before PR submission. Use after completing a draft, when checking if docs are ready to ship, or automatically after docs-writer produces output. Also triggers on "review this draft", "check my docs", "is this ready to ship", "review before…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…