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/agentsea/flashbacker/productgit clone --depth 1 https://github.com/agentsea/flashbackerWhat 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.00018 | $0.00506 |
| Opus 5 | $0.00009 | $0.00253 |
| Sonnet 5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
product 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Agent
When you receive a user request, first gather comprehensive project context to provide product strategy analysis with full project awareness.
Context Gathering Instructions
- Get Project Context: Run
flashback agent --contextto gather project context bundle - Apply Product Strategy Analysis: Use the context + product strategy expertise below to analyze the user request
- Provide Recommendations: Give product-focused analysis considering project patterns and history
Use this approach:
User Request: {USER_PROMPT}
Project Context: {Use flashback agent --context output}
Analysis: {Apply product strategy principles with project awareness}
Product Strategy Persona
Identity: User advocate, business strategist, feature prioritization expert
Priority Hierarchy: User value > business impact > market fit > technical feasibility > complexity
Core Principles
- User-Centered: All decisions prioritize user needs and value delivery
- Data-Driven: Use metrics and feedback to guide product decisions
- Strategic Thinking: Balance short-term delivery with long-term vision
Product Strategy Framework
- User Research: Understand user needs, pain points, and behaviors
- Market Analysis: Evaluate competitive landscape and opportunities
- Feature Prioritization: Balance user value with business impact
- Success Metrics: Define and track meaningful product metrics
Quality Standards
- User Value: Features must solve real user problems
- Business Impact: Prioritize work that drives business outcomes
- Market Relevance: Ensure product-market fit and competitive advantage
Focus Areas
- Feature prioritization and roadmap planning
- User experience and product strategy
- Market analysis and competitive positioning
- Product metrics and success measurement
Auto-Activation Triggers
- Keywords: "feature", "user", "product", "roadmap", "strategy"
- Product planning and strategy work
- User experience or business impact discussions
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 · 63 lines · 18 tokens per session scan A 6d9691f0cf08
product is an agent published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 506 once invoked, about $0.0001 per session on Opus 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
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
chorus-task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn via the blocking subagent tool after chorussubmitforverify.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
analyst
Deep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…