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 skills add nataliacorrea03/claude-code-skills --skill flow-mapgit clone --depth 1 https://github.com/nataliacorrea03/claude-code-skillsWrote 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/nataliacorrea03/claude-code-skills/flow-map)<a href="https://agentmods.dev/skills/nataliacorrea03/claude-code-skills/flow-map"><img src="https://agentmods.dev/badge/skills/nataliacorrea03/claude-code-skills/flow-map/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/skills/nataliacorrea03/claude-code-skills/flow-map"><img src="https://agentmods.dev/badge/skills/nataliacorrea03/claude-code-skills/flow-map.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.00093 | $0.01746 |
| Opus 5 | $0.00046 | $0.00873 |
| Sonnet 5 | $0.00019 | $0.00349 |
| Haiku 4.5 | $0.00009 | $0.00175 |
Grade A, and why
flow-map 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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flow-map
Audit an automation system end to end and render it as one dark, interactive, single-file HTML data-flow map: four columns (Sources → Agents/routines → Stores → Outbox), hover any node to isolate its flows, plus a Schedule tab and a Changed tab.
Core principle: the map only shows what you can prove is running. Live state is the source of truth. Docs, memory files, and the user's own description are leads, not evidence. Anything you can't verify gets flagged as unverified, never silently drawn as fact.
Step 0 — Scope
One quick question before touching anything: what system are we mapping? (work vs personal vs everything, one machine vs several, include on-demand tools or scheduled-only). Default: scheduled + event-driven things that move data, on this machine plus connected cloud services. On-demand tools only if they're part of a running flow.
Step 1 — Discover from live state
Enumerate every scheduler surface that exists on this platform. Check each; skip what doesn't apply. Record WHERE you verified each item (this becomes your evidence list).
| Surface | How to enumerate |
|---|---|
| Cloud scheduled agents / routines | The platform's trigger/cron API (list ALL, note enabled vs disabled). Read the LIVE prompt or config, not a local copy. |
| macOS LaunchAgents | ls ~/Library/LaunchAgents/, then read each plist for schedule + what script it runs. Read the script's header to learn what it actually does. |
| Unix cron / systemd | crontab -l, systemctl list-timers |
| Windows | schtasks /query |
| CI crons | .github/workflows/*.yml schedule blocks, GitLab schedules |
| No-code automations | Zapier/Make/n8n dashboards, Notion/Airtable native automations, Slack workflows. Often not enumerable from the CLI: this is an interview question. |
| Webhooks / event-driven | App code (route handlers), Supabase/Firebase functions, form triggers. Also an interview question if code isn't local. |
For each item found, extract: name, schedule, runtime/model, what it reads, what it writes, guardrails (what it must never touch), status (live / needs work / off-dead / on-demand), and any recent change worth flagging.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 96 lines · 93 tokens per session scan A c4e39476adde
flow-map is a skill published in the GitHub repository nataliacorrea03/claude-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 1,746 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
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.