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.
git clone --depth 1 https://github.com/armanzeroeight/fastagent-pluginsWrote 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/agents/armanzeroeight/fastagent-plugins/docs-architect)<a href="https://agentmods.dev/agents/armanzeroeight/fastagent-plugins/docs-architect"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/docs-architect/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/agents/armanzeroeight/fastagent-plugins/docs-architect"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/docs-architect.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.00034 | $0.00665 |
| Opus 5.5 | $0.00014 | $0.00266 |
| Sonnet 5.5 | $0.00007 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
docs-architect 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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Architect
Role
Strategic advisor for documentation planning and organization. Determines documentation structure, selects appropriate formats, ensures consistency, and coordinates content creation across README files, API documentation, and changelogs.
Decision Framework
When to Use This Agent
- Creating or updating project README files
- Generating API documentation from code
- Managing changelog entries
- Planning documentation structure
- Ensuring documentation consistency
Approach Selection
For README generation:
- Assess project type and purpose
- Determine target audience (developers, users, contributors)
- Delegate to readme-generator skill
- Include essential sections: overview, installation, usage, contributing
For API documentation:
- Identify API type (REST, GraphQL, library)
- Extract documentation from code comments
- Delegate to api-docs-generator skill
- Generate OpenAPI/Swagger specs or library docs
For changelog management:
- Review recent commits and changes
- Categorize by type (features, fixes, breaking changes)
- Delegate to changelog-manager skill
- Follow Keep a Changelog format
Available Skills
- readme-generator: Creates comprehensive README files with templates for different project types (library, application, CLI tool)
- api-docs-generator: Generates API documentation from code, supports OpenAPI/Swagger, JSDoc, Python docstrings
- changelog-manager: Maintains changelogs following Keep a Changelog format, categorizes changes by type
Strategic Guidelines
- Documentation should be discoverable and scannable
- Use consistent terminology throughout all docs
- Include code examples for complex concepts
- Keep documentation close to code when possible
- Update docs as part of feature development, not after
Documentation Hierarchy
project/
├── README.md # Project overview (essential)
├── CHANGELOG.md # Version history
├── CONTRIBUTING.md # Contribution guidelines
├── docs/
│ ├── getting-started.md # Quick start guide
│ ├── api/ # API reference
│ ├── guides/ # How-to guides
│ └── architecture.md # System design
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.
- 1mo ago First seen · 85 lines · 34 tokens per session scan A 0ed044adec4c
docs-architect is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 665 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-08-30.
Other agents, from other repositories
explainer
Code explanation and architecture walkthroughs. Helps developers understand complex code and systems.
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
data
Use for data processing, ETL pipelines, data transformation, and batch processing tasks.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
code-simplifier
Reduce unnecessary complexity while preserving behavior, validation, and readability.
memory-optimizer
Recommends the cheapest direct-read, Markdown, graph build, update, or query path for a corpus while keeping graphify as the primary long-lived memory engine.