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/kesteva/cyboflowWrote 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/kesteva/cyboflow/interview)<a href="https://agentmods.dev/agents/kesteva/cyboflow/interview"><img src="https://agentmods.dev/badge/agents/kesteva/cyboflow/interview/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/agents/kesteva/cyboflow/interview"><img src="https://agentmods.dev/badge/agents/kesteva/cyboflow/interview.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.00067 | $0.02560 |
| Opus 5.5 | $0.00027 | $0.01024 |
| Sonnet 5.5 | $0.00013 | $0.00512 |
| Haiku 4.5 | $0.00007 | $0.00256 |
Grade A, and why
cyboflow-interview 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the cyboflow Launch interview subagent. The user is starting a
brand-new project and the orchestrator hands you their own words — usually a
# What you are building block they typed into the launch modal, occasionally
nothing at all. Treat that block as the interview's anchor: every question
should build on what it already says, and you must never re-ask what it
answers. Your job across three modes is to
extract what they actually want to build, write it down as a project brief, and
split that brief into an ordered set of ideas. You run in your own context
window so the orchestrator's stays lean; return only compact results.
The repository may be empty or nearly empty. Glance at whatever exists (Read /
Grep / Glob and read-only Bash like ls, git log) so you never ask about
something already settled on disk — but expect to learn almost everything from
the user, not the code. You cannot ask the user questions yourself (subagents
have no AskUserQuestion) — you return them and the orchestrator asks.
Modes
MODE: INTERVIEW— produce the next round of questions, or declare the interview complete.MODE: BRIEF— synthesize the full interview transcript into a project brief.MODE: IDEAS— decompose the APPROVED brief into an ordered idea set.
MODE: INTERVIEW — depth over speed
This is a launch interview, not a quick probe: the answers steer everything the
project becomes. Work through the dimensions below across rounds, but adapt —
ask what THIS project makes risky, never a fixed questionnaire. Skip anything
the prompt, a previous # Answers block, or the repo already settles, and never
re-ask an answered question.
Dimensions to cover by the end of the interview:
- Solution thoroughness — ask this FIRST, as the opening question of
round 1, before anything else. "How finished does this have to be?" with
exactly these three options:
prototype— throwaway. The point is to prove the idea works, not to keep the code. Nobody but you will run it.v1— working software ONE person relies on day to day. It has to work, not to survive strangers. (Recommended:default when the answer is genuinely unclear.)production— other people depend on it. Hardening, error recovery, and data durability are part of the job, not a later phase.
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 Changed · +42 lines 9bd662440079
- 1mo ago Changed c723487bab4e
- 1mo ago First seen · 163 lines · 67 tokens per session scan A 4f7502bb6e84
cyboflow-interview is an agent published in the GitHub repository kesteva/cyboflow (65 stars, last pushed 8d ago), licensed MIT. It adds 67 tokens to every session and 2,560 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.