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.
Borrowing it
Nothing to install: this file belongs to strands-agents/harness-sdk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/strands-agents/harness-sdk/main/.agents/skills/docs-writer/SKILL.mdgit 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/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/strands-agents/harness-sdk/docs-writer"><img src="https://agentmods.dev/badge/skills/strands-agents/harness-sdk/docs-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.01755 |
| Opus 5.5 | $0.00030 | $0.00702 |
| Sonnet 5.5 | $0.00015 | $0.00351 |
| Haiku 4.5 | $0.00007 | $0.00176 |
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 15d 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 follow
../../references/diagrams.md. Concept diagrams are hand-authored SVGs rendered with<Diagram>; use thedocs-diagramsskill to draw them.```mermaidfences are fine for quick or short-lived diagrams. Never use ASCII art or box-drawing characters for diagrams.
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.
- 15d ago Changed 7dba5f84fa95
- 2mo 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 (8,996 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 1,755 once invoked, about $0.0003 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.
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.
agentscope-java
Expert Java developer skill for AgentScope Java framework - a reactive, message-driven multi-agent system built on Project Reactor. Use when working with reactive programming, LLM integration, agent orchestration, multi-agent systems, or when the user mentions AgentScope, ReActAgent, Mono/Flux, Project Reactor, or…
apply-patch
Apply multi-file or tricky edits atomically with git apply instead of many fragile editfile calls. Use when changing several files at once or when editfile fails to match.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
synthesize-report
Produces a citation-grounded summary across one or more workspace source files for summaries, briefings, literature reviews, or comparisons.