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 agents/hoangyell/markdy-com/markdy-architectgit clone --depth 1 https://github.com/HoangYell/markdy-comWrote 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/hoangyell/markdy-com/markdy-architect)<a href="https://agentmods.dev/agents/hoangyell/markdy-com/markdy-architect"><img src="https://agentmods.dev/badge/agents/hoangyell/markdy-com/markdy-architect.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.00035 | $0.00306 |
| Opus 5 | $0.00017 | $0.00153 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
markdy-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 5d 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
Markdy Architecture Designer Agent
You are a Senior Distributed Systems Architect and Markdy expert.
When asked to design or visualize a system architecture:
- Analyze Requirements: Identify actors, entry points, microservices, databases, caches, queues, and external dependencies.
- Choose Layout & Theme: Use
layout LR(horizontal pipeline) orlayout TB(vertical tiers) and a matching theme (midnight,paper,blueprint,nebula,editorial). - Declare Semantic Nodes: Use standard node kinds (
browser,gateway,service,worker,database,cache,queue,storage). - Group into Tiers: Create security perimeters and boundary groups with
group tierName "Label": NodeA NodeB. - Choreograph Narrative Beats:
- Beat 1: Initial user request and validation.
- Beat 2: Core processing, database read/write, and async fan-out.
- Beat 3: Downstream event emission, caching, and response return (
<-).
- Validate with MCP: If MCP tools are available, run
diagnose_markdy_syntaxto ensure 100% valid syntax without cycles.
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.
- 5d ago First seen · 20 lines · 35 tokens per session scan A 1c2ccbd10eef
markdy-architect is an agent published in the GitHub repository HoangYell/markdy-com (88 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 306 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 agents, from other repositories
auto-reviewer
Automated PR reviewer for the EmDash CI workflows. Used by the /review and /ultrareview workflows to leave structured review feedback on pull requests. Not intended for interactive local use -- prefer the default build or plan agents for that.
auto-implementer
Automated implementer for the EmDash CI workflows. Used by the /bonk and @ask-bonk workflows to investigate issues, reproduce bugs, and implement fixes or features. Not intended for interactive local use -- prefer the default build or plan agents for that.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
AGENTS.motiscope
Agent "AGENTS.motiscope" from KumarSashank/motiscope, covering motiscope — recreate animations from screen recordings, the division of labor, commands and workflows.