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/saajunaid/caddis-pluginWrote 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/commands/saajunaid/caddis-plugin/generate-hld-lld)<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/generate-hld-lld"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/generate-hld-lld/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/commands/saajunaid/caddis-plugin/generate-hld-lld"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/generate-hld-lld.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.00017 | $0.00287 |
| Opus 5.5 | $0.00007 | $0.00115 |
| Sonnet 5.5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
generate-hld-lld 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.
What it actually says
Generate Architecture Document (HLD / LLD)
Create a formal, enterprise-grade architecture deliverable from our living documentation.
Instructions
- Load the architecture document skill: Read
.github/skills/docs/architecture-document/SKILL.md - Read the living architecture doc: Read
docs/Architecture.mdcompletely - Read project config: Read
.github/project-config.mdfor org name, tech stack, branding - Follow the Generation Workflow in the skill (Steps 1-5)
- Apply document metadata rules: Any Markdown companion output or source-doc update must follow
.github/instructions/document-frontmatter.instructions.md; for DOCX/PPTX deliverables, mirror the same author/date/model metadata on the cover page or revision history. - Ask me: HLD, LLD, or both? DOCX, PPTX, or both?
Quick Triggers
- "Generate HLD" → Full High-Level Design document
- "Generate LLD" → Full Low-Level Design document
- "Generate HLD for {component}" → Scoped to one subsystem
- "Architecture deck" → Executive summary PPTX
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 · 26 lines · 17 tokens per session scan A 103904925405
generate-hld-lld is a command published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 287 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-09.
Other commands, from other repositories
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
accept
Command dispatcher for accept.
change
Command dispatcher for change.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.