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/vladm3105/aidoc-flow-frameworkWrote 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/vladm3105/aidoc-flow-framework/contact-us)<a href="https://agentmods.dev/commands/vladm3105/aidoc-flow-framework/contact-us"><img src="https://agentmods.dev/badge/commands/vladm3105/aidoc-flow-framework/contact-us.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.00015 | $0.00284 |
| Opus 5 | $0.00008 | $0.00142 |
| Sonnet 5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
contact-us 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.
What it actually says
Contact Us
Print the available contact channels for the aidoc-flow project, one line each. Static output; no file reads, no shell calls.
Instructions
-
Print the channels block verbatim:
aidoc-flow — contact Repository: https://github.com/vladm3105/aidoc-flow-framework Issues (bugs): https://github.com/vladm3105/aidoc-flow-framework/issues Maintainer: @vladm3105 (GitHub) For bug reports: /aidoc-flow:bug-report For feedback: /aidoc-flow:feedback -
Stop. Do not invent additional channels (Slack, Discord, email) — if a channel is not listed here, it does not exist for this project yet.
Maintenance
When a new contact channel is added (Discussions, mailing list, etc.), update this file directly. The command output is intentionally hand-edited rather than auto-discovered to avoid surfacing channels that are not yet ready.
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 · 41 lines · 15 tokens per session scan A ef245a089bce
contact-us is a command published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 284 once invoked, about $0.0001 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 commands, from other repositories
create-command
Create a new obsidian-second-brain command via interview - zero markdown editing required.
obsidian-health
Run a vault health check - grouped by severity, detects contradictions, concept gaps, stale claims, and structural issues.
obsidian-architect
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions. Re-run to refresh without clobbering your edits.
obsidian-retrieval-eval
Measure how well vault search finds the right note for a natural-language question - recall@k and MRR, with the concrete failures.
obsidian-visualize
Generate a visual canvas map of your vault - see the shape of your second brain and how knowledge connects.
obsidian-export
Export a clean structured snapshot of the vault that any agent or tool can consume - flat JSON, markdown index, or an OKF (Open Knowledge Format) bundle.