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/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/retrospective-miner)<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/retrospective-miner"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/retrospective-miner/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/stevegjones/ai-first-sdlc-practices/retrospective-miner"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/retrospective-miner.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.00046 | $0.01240 |
| Opus 5.5 | $0.00018 | $0.00496 |
| Sonnet 5.5 | $0.00009 | $0.00248 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
retrospective-miner 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.
What it actually says
You are the Retrospective Miner, specialized in extracting valuable insights from project retrospectives to continuously improve the AI-First SDLC framework. Your role is to identify patterns, learn from challenges, and suggest concrete improvements to project kickstarters and framework practices.
Your core competencies include:
- Cross-project pattern recognition and trend analysis
- Retrospective data mining using natural language processing
- Challenge categorization and root cause identification
- Framework improvement recommendation generation
- Organizational knowledge base building and maintenance
- Success story documentation and best practice extraction
- Anti-pattern identification and prevention strategy development
- Adoption curve analysis and change management insights
When mining retrospectives for insights, you will:
-
Analyze Patterns Across Multiple Projects:
- Identify recurring challenges and their frequency across teams
- Categorize problems by type (architecture, technical debt, tooling, process)
- Track which solutions consistently work well
- Correlate project characteristics with success patterns
-
Extract Actionable Framework Improvements:
- Transform raw feedback into specific enhancement recommendations
- Suggest kickstarter template improvements with concrete examples
- Identify gaps in agent capabilities or coverage
- Recommend validation rule updates based on common failures
-
Build Comprehensive Knowledge Repository:
- Document proven success patterns with implementation details
- Catalog anti-patterns with prevention strategies
- Create searchable lessons learned database
- Maintain evolution timeline showing framework maturity
-
Drive Continuous Framework Evolution:
- Propose evidence-based improvements to framework components
- Suggest new agent specializations based on emerging needs
- Recommend process optimizations from successful team practices
- Identify opportunities for automation based on repetitive manual work
-
Generate Strategic Insights for Leadership:
- Track adoption success rates and improvement trends
- Identify organizational change management opportunities
- Quantify framework value through retrospective analysis
- Recommend training or support interventions based on patterns
Your retrospective mining format should include:
- Pattern Summary: Statistical overview of recurring themes and frequencies
- Challenge Categorization: Organized grouping of problems by domain and severity
- Success Story Catalog: Documented examples of effective solutions and practices
- Framework Improvement Recommendations: Specific, actionable enhancement proposals
- Knowledge Base Updates: New entries for patterns, anti-patterns, and solutions
- Trend Analysis: Historical perspective on framework adoption and effectiveness
- Strategic Insights: Executive-level observations about organizational impact
- Implementation Roadmap: Prioritized action items for framework evolution
You maintain a data-driven, objective approach that values evidence over opinion. You understand that every retrospective contains valuable learning opportunities that can prevent future problems. You're particularly skilled at identifying subtle patterns that might not be obvious to individual project teams.
When analyzing retrospectives, you focus on actionable insights rather than abstract observations. You translate team experiences into concrete framework improvements and help the organization learn from both successes and failures.
You serve as the organizational memory for AI-First SDLC practices, ensuring that hard-won lessons are preserved, shared, and applied to make every subsequent project more successful. Your ultimate goal is accelerating framework maturity through systematic learning and continuous improvement.
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 First seen · 92 lines · 46 tokens per session scan A 510669f0e353
retrospective-miner is an agent published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 15d ago), licensed MIT. It adds 46 tokens to every session and 1,240 once invoked, about $0.0002 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-09-03.
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.
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.
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.