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 pe-menezes/vibeflow --skill vibeflow-teachgit clone --depth 1 https://github.com/pe-menezes/vibeflowWrote 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/pe-menezes/vibeflow/vibeflow-teach)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow/vibeflow-teach"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-teach/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/pe-menezes/vibeflow/vibeflow-teach"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/vibeflow-teach.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.00057 | $0.01961 |
| Opus 5 | $0.00028 | $0.00981 |
| Sonnet 5 | $0.00011 | $0.00392 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade C, and why
vibeflow-teach scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
A clone gets removed with `rm -rf "$REPO_PATH"` — never `rm -rf` without an How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibeflow: Teach
Teach the project knowledge base. Update .vibeflow/ docs with
corrections, new conventions, decisions, or patterns based on
natural language feedback. Also imports patterns from external
reference repos via --from <url|path>.
Usage: Provide your feedback as input, or use --from <url|path> to import from an external repo.
Language
Detect the language of the user's input. Write ALL output in that same language. Technical terms in English are acceptable regardless of the detected language.
The one rule that governs every edit
When editing an existing generated region, everything you write goes
outside the <!-- vibeflow:auto:start/end --> markers — that is what makes
a correction survive the next incremental analyze. Read the target file before
editing it, and never rewrite what is inside the markers; analyze owns that
region. One explicit exception: a new pattern doc created in category (d) is
born with its own markers and its initial content inside them, so analyze owns
that region from the start.
Before starting
.vibeflow/ has to exist: read .vibeflow/index.md directly by path for
orientation. If it isn't there, stop with ".vibeflow/ does not exist. Run
the vibeflow-analyze skill first to create the knowledge base." — don't create it by hand.
Then branch on the input: --from in the input goes to Import from external
repo; anything else goes to Classify the feedback.
Import from external repo
Imports patterns and conventions from an external reference repo — shared architecture docs, coding guidelines.
Step 1: Parse arguments
Take the <url|path> after --from. The repo name is --name <alias> when
given, otherwise derived: the URL's last path segment without .git
(https://github.com/org/platform-patterns.git → platform-patterns), or the
directory name for a local path (./my-patterns → my-patterns).
Step 2: Get the repo
A URL (contains :// or starts with git@) is cloned shallow into a temp
directory — git clone --depth 1 <url> $TMPDIR/vibeflow-teach-$(date +%s) —
$REPO_PATH is set to that directory, and the clone is marked for cleanup. A
local path is verified to exist and be a directory, and $REPO_PATH is set to
its resolved absolute path; nothing to clean up.
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.
- 3d ago Changed · -1 lines · -2 tokens per session 6a8709473716
- 10d ago First seen · 237 lines · 59 tokens per session scan C 5f2b8969bfbd
vibeflow-teach is a skill published in the GitHub repository pe-menezes/vibeflow (29 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 1,961 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
instruction-maintainer
Detect reusable rules in user corrections or manual rewrites of AI output, ask whether they should be persisted into copilot-instructions or scoped instructions, and maintain them with minimal changes.
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
ijfw-memory-audit
Audit and clean project memory files. Trigger: 'memory audit', 'clean memory', 'memory health', /memory-audit.
ijfw-handoff
Session handoff generation and loading. Trigger: session end, context full, /handoff.
ijfw-summarize
Generate optimized project context from codebase scan. Trigger: new project, no CLAUDE.md, /ijfw-summarize.
repo-context-ledger
Record every behavior-changing feature addition, fix, and adjustment as durable, evidence-based repository knowledge, then use that ledger to continue accurately across AI windows, tools, Git collaboration, and pull requests. Use the deterministic runtime to route bounded context, isolate private drafts, publish…