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/alexei-led/architect/tools-report-markdownnpx skills add alexei-led/architect --skill tools-report-markdowngit clone --depth 1 https://github.com/alexei-led/architectWrote 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/alexei-led/architect/tools-report-markdown)<a href="https://agentmods.dev/skills/alexei-led/architect/tools-report-markdown"><img src="https://agentmods.dev/badge/skills/alexei-led/architect/tools-report-markdown.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.1 | $0.00106 | $0.01045 |
| Opus 5 | $0.00053 | $0.00522 |
| Sonnet 5 | $0.00021 | $0.00209 |
| Haiku 4.5 | $0.00011 | $0.00104 |
Grade A, and why
tools-report-markdown 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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report and Markdown tools
The report is an artifact a human reads and a tool re-parses. These tools keep its frontmatter machine-valid and its diagrams renderable, and they catch broken links and typos before the report ships.
Evidence dimension: report (quality of the artifact, not the architecture).
When to use
Use during the write-the-report step and before declaring a report or plan done. First decide the audience:
- Human-facing reports: consider a small Mermaid diagram for the system map, dependency clusters, or boundary drift when it improves comprehension.
- AI/agent-targeted reports: prefer plain text adjacency lists, cited bullets, and compact structure. Do not spend tokens on fancy diagrams, broad tables, or formatting polish; models do not read diagrams as evidence.
Use to validate YAML frontmatter parses, render human-facing diagrams when chosen, and check links/spelling. Scope checks to the target report or plan; broaden to repo-wide docs only when the user asks. Diagrams are summaries for people, not architecture evidence.
Commands
Use the repo's detected package runner for Node-based formatters. The example
uses npm exec; substitute pnpm exec, bunx, or the configured script when
that is the project runner.
# Validate report frontmatter with the authoritative helper
architect-validate-report report.md
# Extract frontmatter for quick local jq/yq checks
python -c 'from pathlib import Path; print(Path("report.md").read_text().split("---", 2)[1])' > /tmp/report-frontmatter.yaml
yq -o=json '.' /tmp/report-frontmatter.yaml | jq '.tool_coverage'
# Optional for human-facing reports: render a Mermaid diagram to SVG
mmdc -i map.mmd -o map.svg
# Graphviz / D2 for graphs produced by pydeps, goda, go-callvis
dot -Tsvg graph.dot -o graph.svg
d2 graph.d2 graph.svg
# Link check (catches dead evidence refs and doc links)
lychee report.md
# Spelling (technical dictionary as needed)
codespell report.md
# Format check for the target artifact(s), using the repo's package runner
npm exec -- prettier --check report.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.
- 6d ago First seen · 114 lines · 106 tokens per session scan A 32502f1aa68f
tools-report-markdown is a skill published in the GitHub repository alexei-led/architect (2 stars, last pushed 1mo ago), licensed MIT. It adds 106 tokens to every session and 1,045 once invoked, about $0.0005 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-31.
Other skills, from other repositories
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…