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 joaoguirunas/team-os --skill dev-technical-writinggit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/dev-technical-writing)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/dev-technical-writing"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/dev-technical-writing/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/joaoguirunas/team-os/dev-technical-writing"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/dev-technical-writing.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.00036 | $0.00972 |
| Opus 5.5 | $0.00014 | $0.00389 |
| Sonnet 5.5 | $0.00007 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
dev-technical-writing 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 27d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writing para Software Complexo
ADR — Architecture Decision Record
Toda decisão arquitetural relevante deve ser documentada em docs/decisions/YYYY-MM-DD-{slug}.md.
Template ADR
# ADR-{NNN}: {Título da Decisão}
**Data:** YYYY-MM-DD
**Status:** Proposto | Aceito | Depreciado | Substituído por ADR-{NNN}
**Contexto:** {O problema que precisa ser resolvido. Forças em jogo.}
## Decisão
{A decisão tomada, explicada de forma direta.}
## Consequências
**Positivas:**
- {benefício 1}
**Negativas:**
- {trade-off 1}
## Alternativas Consideradas
| Alternativa | Por que descartada |
|---|---|
| {opção A} | {motivo} |
## Diagrama (se aplicável)
\`\`\`mermaid
graph TD
A[Cliente] --> B[API Gateway]
B --> C[Auth Service]
B --> D[Core Service]
\`\`\`
Module Spec
Documentação de módulo em docs/modules/{module-name}.md.
Template Module Spec
# Módulo: {Nome}
**Responsabilidade:** {Uma frase descrevendo o que este módulo faz}
**Owner:** {Agente ou pessoa responsável}
## Interface pública
\`\`\`typescript
// Exports principais
export function {functionName}(params: {ParamsType}): {ReturnType}
\`\`\`
## Dependências
- **Requer:** {módulos que este consome}
- **Expõe para:** {módulos que consomem este}
## Fluxo de dados
\`\`\`mermaid
sequenceDiagram
participant C as Client
participant M as {Module}
participant D as Database
C->>M: request
M->>D: query
D-->>M: result
M-->>C: response
\`\`\`
## Decisões relevantes
- [ADR-{NNN}]({link}) — {título}
Smart Memory — Formato Obsidian
Documentos em docs/smart-memory/ usam frontmatter com links relativos para navegação:
---
title: {Título}
type: overview | story | decision | schema | research | task-log
agent: {nome-do-agente}
created: YYYY-MM-DD
updated: YYYY-MM-DD
tags: [tag1, tag2]
related: ["[[caminho/relativo]]"]
---
Links internos entre documentos: [[caminho/relativo]] — compatível com Obsidian.
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.
- 27d ago Changed e6d324b03a73
- 1mo ago First seen · 156 lines · 36 tokens per session scan A 7b475d0a979f
dev-technical-writing is a skill published in the GitHub repository joaoguirunas/team-os (5 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 972 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
jtbd-framing
The Jobs-to-be-Done framework as applied product methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity (discovery, prioritization, positioning) and where it becomes performative ritual (job-statement…
jev-integrate
Wire a System One model (Jev, or an open reproduction like Von) into a product feature — routing, guardrails, scoring, classification. Use when replacing an LLM call that returns a label rather than prose, when adding a typed decision to an agent loop, or when deciding between the hosted Jev API and a local open…
mcp-server-builder
Use to build, wire up, or debug an MCP (Model Context Protocol) server that gives Claude access to an internal API, database, or SaaS tool. Trigger when the user wants Claude to connect to their own system, asks for an MCP server, needs custom tools for Claude Code or the Claude app, or an existing server's tools are…
email-template-generator
Generate professional email templates for various business scenarios including sales outreach, customer support, internal communications, follow-ups, and apologies. Creates personalized, tone-appropriate templates with subject lines and formatting. Use when users need to write business emails, cold outreach, or…