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/rakaarwaky/qwen-web-arwaky/add-docs-pythonnpx skills add rakaarwaky/qwen-web-arwaky --skill add-docs-pythongit clone --depth 1 https://github.com/rakaarwaky/qwen-web-arwakyWrote 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/rakaarwaky/qwen-web-arwaky/add-docs-python)<a href="https://agentmods.dev/skills/rakaarwaky/qwen-web-arwaky/add-docs-python"><img src="https://agentmods.dev/badge/skills/rakaarwaky/qwen-web-arwaky/add-docs-python.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.00038 | $0.01333 |
| Opus 5 | $0.00019 | $0.00666 |
| Sonnet 5 | $0.00008 | $0.00267 |
| Haiku 4.5 | $0.00004 | $0.00133 |
Grade A, and why
add-docs-python 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 4d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
add-docs-python
Purpose
Add documentation at correct locations following project conventions.
Document Location Matrix
| Document | Location | Audience | Focus |
|---|---|---|---|
| PRD.md | Root workspace | Stakeholder, PM, Design, Eng | What & Why |
| README.md | Root workspace | Developer (new/existing) | How to use/run |
| FRD.md | Each feature module | Engineer, QA, Tech Lead | How (functionally) |
Rules
- PRD.md = Product Requirements Document — 1 per project root — describes WHAT and WHY for stakeholders.
- README.md = Developer onboarding — 1 per project root — describes HOW TO USE/RUN for developers.
- FRD.md = Functional Requirements Document — 1 per feature module — describes HOW (functionally) for engineers.
- Relationship: PRD (what/why) → FRD (how) → README (how to use). Each serves a different audience.
- All public classes and functions MUST have docstrings (PEP 257).
- Docstrings MUST explain "what" and "why", not "how" (code shows how).
Templates
PRD.md
# PRD — <project-name>
## Problem Statement
<One paragraph: what problem does this project solve?>
## Goals & Success Metrics
- Goal 1: <measurable outcome>
- Goal 2: <measurable outcome>
## User Personas
- **Persona 1**: <who they are, what they need>
- **Persona 2**: <...>
## Scope
- In scope: <...>
- Out of scope: <...>
## Feature Requirements (Prioritized)
### P0 — Must Have
- [ ] <feature with acceptance criteria>
### P1 — Should Have
- [ ] <feature with acceptance criteria>
### P2 — Nice to Have
- [ ] <feature with acceptance criteria>
## Non-functional Requirements (High-level)
- Performance: <...>
- Security: <...>
- Scalability: <...>
## Open Questions / Risks
- <question or risk>
FRD.md
# FRD — <feature-name>
## System Overview
<Architecture diagram or high-level description>
## Functional Requirements
### FR-001: <Feature Name>
- **Description**: <what it does>
- **Input**: <input data>
- **Output**: <output data>
- **Business Rules**: <validation logic>
- **Edge Cases**: <edge case handling>
- **Error Handling**: <error scenarios>
### FR-002: <Feature Name>
- ...
## API Contract
| Operation | Input | Output | Description |
|-----------|-------|--------|-------------|
| `<name>` | ... | ... | ... |
## Integration Points
- **3rd Party**: <service name, purpose>
- **Internal**: <service name, purpose>
## Non-functional Requirements (Detailed)
- Performance: <response time, throughput>
- Security: <auth, encryption, compliance>
- SLA: <availability, uptime>
## Test Scenarios / QA Checklist
- [ ] <test scenario with expected result>
## Assumptions & Constraints
- <assumption or constraint>
## Glossary
- **Term**: <definition>
## Reference
- PRD: <link to root PRD.md>
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.
- 4d ago First seen · 234 lines · 38 tokens per session scan A 3e7c33a74ae8
add-docs-python is a skill published in the GitHub repository rakaarwaky/qwen-web-arwaky (11 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,333 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…