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 agentmods add agents/eco-ansible-content/agentic-workflows/quickstartgit clone --depth 1 https://github.com/eco-ansible-content/agentic-workflowsWhat 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 | $0.00000 | $0.00729 |
| Opus 5 | $0.00000 | $0.00365 |
| Sonnet 5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
QUICKSTART 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 2d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Start Guide - Windows Collection Swarm
One-Command Deployment
/windows-collection-swarm ANSTRAT-12345
Replace ANSTRAT-12345 with your Jira Epic key.
What Happens
-
Jira Analysis (2-5 min)
- Recursively analyzes Epic and all sub-tasks
- Creates module backlog in
docs/plans/module_backlog.md
-
Workspace Setup (1-2 min)
- Creates
~/agentic-workflow-collections/<namespace>/<name>/ - Copies Jarvis templates and baseline files
- Creates
-
Module Building (60-90 min for 30 modules)
- Builds modules in parallel batches of 3-5
- Each module tested with 4-stage loop
- All code peer-reviewed
-
Refactoring (15-20 min total)
- Runs every 10 modules
- Extracts common code to utilities
-
Delivery (5-10 min)
- Four-pillar audit
- Git commit and push
Monitoring Progress
# Watch the backlog
watch -n 10 "grep -c '\[x\]' ~/agentic-workflow-collections/*/*/docs/plans/module_backlog.md"
# Count modules built
ls ~/agentic-workflow-collections/*/*/plugins/modules/*.ps1 | wc -l
# View git commits
cd ~/agentic-workflow-collections/<namespace>/<name>
git log --oneline
Success Indicators
✅ Module backlog file created
✅ Collection directory scaffolded
✅ Modules appearing in plugins/modules/
✅ Tests passing (check test output)
✅ Git commits being made
✅ Final push to remote repository
Troubleshooting
Nothing Happens
- Check Jira credentials:
jira-rh epic list <KEY> - Verify Epic key format: Should be
PROJECT-NUMBER
Modules Not Building
- Check module backlog:
cat docs/plans/module_backlog.md - Review agent output in Claude Code session
Tests Failing
- QA Coordinator auto-fixes (3 attempts)
- If persistent, check Windows host connectivity
Git Push Fails
- Verify git credentials:
git push origin main - Check network connectivity
Advanced Options
# Custom namespace and name
/windows-collection-swarm ANSTRAT-12345 namespace=microsoft collection_name=hyperv
# Larger batches (faster, more resource-intensive)
/windows-collection-swarm ANSTRAT-12345 batch_size=5
# Smaller batches (slower, more stable)
/windows-collection-swarm ANSTRAT-12345 batch_size=2
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.
- 2d ago First seen · 119 lines · 0 tokens per session scan A 192638c4cf5c
QUICKSTART is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 729 tokens. 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 agents, from other repositories
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
dependency-blocker-monitor
Use when monitoring workcell BOM dependencies and cell health to open or resolve blocker issues when a cell fails or recovers. USE FOR: read workcell BOM dependencies, monitor cell deployment status, create blocker issues, and resolve them on recovery. DO NOT USE FOR: general incident response, application code, or…