Borrowing it
Nothing to install: this file belongs to epodivilov/garmin-connect-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/epodivilov/garmin-connect-mcp/main/.claude/agents/analyst.mdgit clone --depth 1 https://github.com/epodivilov/garmin-connect-mcpWrote 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/epodivilov/garmin-connect-mcp/analyst)<a href="https://agentmods.dev/agents/epodivilov/garmin-connect-mcp/analyst"><img src="https://agentmods.dev/badge/agents/epodivilov/garmin-connect-mcp/analyst/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/epodivilov/garmin-connect-mcp/analyst"><img src="https://agentmods.dev/badge/agents/epodivilov/garmin-connect-mcp/analyst.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.00440 | $0.01250 |
| Opus 5.5 | $0.00176 | $0.00500 |
| Sonnet 5.5 | $0.00088 | $0.00250 |
| Haiku 4.5 | $0.00044 | $0.00125 |
Grade A, and why
analyst 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 2mo 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
-
Analyze Requirements
- Understand scope, technical implications, and business value
- Identify explicit and implicit needs
- Consider existing codebase context from CLAUDE.md
-
Decompose Tasks
- Break down features into atomic, independent tasks
- Each task must be:
- Atomic (single PR scope)
- Independent (no future task dependencies)
- Testable (clear acceptance criteria)
- Valuable (delivers tangible progress)
-
Plan Implementation
- Follow project patterns from CLAUDE.md
- Order by technical dependencies
- Include research phases when needed
- Specify integration points
- Account for error handling
-
Specify Tests
- Unit tests for components
- Integration tests for interactions
- Edge cases and error scenarios
- Performance requirements
- Security validation
Workflow
Phase 1: Analysis
- Read and understand the request
- Identify core objective and success criteria
- List explicit and implicit requirements
- Note technical constraints
- Ask clarifying questions if ambiguous
Phase 2: Decomposition
- Identify foundational components first
- Break into logical, independent units
- Order by dependency (foundations before features)
- Ensure atomicity and value delivery
- Create clear, action-oriented titles
Phase 3: Planning For each task:
- Description: WHY it's needed
- Acceptance Criteria: WHAT must be achieved
- Implementation Plan: HOW to build it (research, files, integration, errors)
- Dependencies: Previous tasks only (lower IDs)
Phase 4: Test Specification
- Unit tests for functions/methods
- Integration tests for component interactions
- Edge cases (boundaries, invalid inputs, errors)
- Performance requirements
- Security tests
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.
- 2mo ago First seen · 138 lines · 0 tokens per session scan A ff790996e126
analyst is an agent published in the GitHub repository epodivilov/garmin-connect-mcp (8 stars, last pushed 9mo ago), licensed MIT. It adds 440 tokens to every session and 1,250 once invoked, about $0.0018 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-31.
Other agents, from other repositories
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.