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 sutchan/Agent-Skills-Hub --skill project-workflow-analysis-blueprint-generatorgit clone --depth 1 https://github.com/sutchan/Agent-Skills-HubWrote 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/sutchan/agent-skills-hub/project-workflow-analysis-blueprint-generator)<a href="https://agentmods.dev/skills/sutchan/agent-skills-hub/project-workflow-analysis-blueprint-generator"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/project-workflow-analysis-blueprint-generator/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/sutchan/agent-skills-hub/project-workflow-analysis-blueprint-generator"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/project-workflow-analysis-blueprint-generator.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.00077 | $0.02244 |
| Opus 5 | $0.00039 | $0.01122 |
| Sonnet 5 | $0.00015 | $0.00449 |
| Haiku 4.5 | $0.00008 | $0.00224 |
Grade A, and why
project-workflow-analysis-blueprint-generator 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 yesterday.
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.
This is a copy
97% identical to workflow-analysis-blueprint — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Workflow Documentation Generator
Configuration Variables
${PROJECT_TYPE="Auto-detect|.NET|Java|Spring|Node.js|Python|React|Angular|Microservices|Other"}
<!-- Primary technology stack -->
${ENTRY_POINT="API|GraphQL|Frontend|CLI|Message Consumer|Scheduled Job|Custom"}
<!-- Starting point for the flow -->
${PERSISTENCE_TYPE="Auto-detect|SQL Database|NoSQL Database|File System|External API|Message Queue|Cache|None"}
<!-- Data storage type -->
${ARCHITECTURE_PATTERN="Auto-detect|Layered|Clean|CQRS|Microservices|MVC|MVVM|Serverless|Event-Driven|Other"}
<!-- Primary architecture pattern -->
${WORKFLOW_COUNT=1-5}
<!-- Number of workflows to document -->
${DETAIL_LEVEL="Standard|Implementation-Ready"}
<!-- Level of implementation detail to include -->
${INCLUDE_SEQUENCE_DIAGRAM=true|false}
<!-- Generate sequence diagram -->
${INCLUDE_TEST_PATTERNS=true|false}
<!-- Include testing approach -->
Generated Prompt
"Analyze the codebase and document ${WORKFLOW_COUNT} representative end-to-end workflows
that can serve as implementation templates for similar features. Use the following approach:
Initial Detection Phase
${PROJECT_TYPE == "Auto-detect" ?
"Begin by examining the codebase structure to identify technologies:
- Check for .NET solutions/projects, Spring configurations, Node.js/Express files, etc.
- Identify the primary programming language(s) and frameworks in use
- Determine the architectural patterns based on folder structure and key components"
: "Focus on ${PROJECT_TYPE} patterns and conventions"}
${ENTRY_POINT == "Auto-detect" ?
"Identify typical entry points by looking for:
- API controllers or route definitions
- GraphQL resolvers
- UI components that initiate network requests
- Message handlers or event subscribers
- Scheduled job definitions"
: "Focus on ${ENTRY_POINT} entry points"}
${PERSISTENCE_TYPE == "Auto-detect" ?
"Determine persistence mechanisms by examining:
- Database context/connection configurations
- Repository implementations
- ORM mappings
- External API clients
- File system interactions"
: "Focus on ${PERSISTENCE_TYPE} interactions"}
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.
- yesterday Changed · -5 lines · +59 tokens per session 1563be31e5dd
- 7d ago First seen · 299 lines · 18 tokens per session scan A ea62d6ecb927
project-workflow-analysis-blueprint-generator is a skill published in the GitHub repository sutchan/Agent-Skills-Hub (2 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 2,244 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to workflow-analysis-blueprint, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
skill-authoring
Author SKILL.md skills: frontmatter, validator limits, structure.
skill-creator
Create, improve, evaluate, benchmark skills. Use when authoring a new skill, updating an existing one, running evals, or optimizing a skill's description for triggering. Don't use for invoking skills, writing prose, or scaffolding Python projects.
iflytek-hyper-tts
A text-to-speech tool that turns written text into an MP3 recording. It can use an authorized voice and adjust speaking speed, volume, and pitch.