Borrowing it
Nothing to install: this file belongs to freegyes/project-ContemPlace. 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/freegyes/project-ContemPlace/main/.claude/commands/analyze.mdgit clone --depth 1 https://github.com/freegyes/project-ContemPlaceWrote 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/commands/freegyes/project-contemplace/analyze)<a href="https://agentmods.dev/commands/freegyes/project-contemplace/analyze"><img src="https://agentmods.dev/badge/commands/freegyes/project-contemplace/analyze.svg" alt="Measured on agentmods" 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.00000 | $0.01559 |
| Opus 5 | $0.00000 | $0.00779 |
| Sonnet 5 | $0.00000 | $0.00312 |
| Haiku 4.5 | $0.00000 | $0.00156 |
Grade A, and why
analyze 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 7d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze
Extract project-relevant insights from user-provided input. The user brings material — a session write-up, product feedback, a captured fragment, an error log, a design sketch, a conversation transcript — and you turn it into actionable artifacts: GitHub issues, issue comments, doc updates, ADRs, or memory entries.
Arguments
$ARGUMENTS — optional hint about what the input is or what to focus on (e.g., "clustering session feedback", "fragment about agent onboarding", "this morning's backup failure log"). Can be empty — you'll figure it out from the input.
When to use this vs other commands
/analyze— you have input to process and want insights extracted. No implementation./product-intake— you used the product and want to turn that experience into tracked issues. Deeper than analyze — traces code paths, assesses maturity, produces agent-ready issues./harvest-ideas— you want to search the corpus for product ideas. No external input./audit-captures— you want to evaluate capture quality against the philosophy. Structured evaluation./work-on-issue— you want to implement something, not just analyze.
Workflow
Phase 1: Receive and understand the input
If the user hasn't provided the input yet, ask for it and wait. Don't start analyzing nothing.
Once you have the input, classify it:
| Input type | Example | Typical output |
|---|---|---|
| Session write-up | "I tried using list_clusters and here's what happened..." | Feature refinements, UX observations, product value examples |
| Captured fragment | A ContemPlace note ID or pasted text | Connections to existing issues, new issue candidates, design implications |
| Product feedback | "This felt clunky because..." | UX issues, design tensions, improvement candidates |
| Error/failure log | A stack trace, CI log, or error message | Root cause analysis, fix candidates, issue creation |
| Design sketch | A rough idea, wireframe description, or feature concept | Design questions, feasibility assessment, issue creation |
| Conversation transcript | A discussion that produced decisions or ideas | Decision extraction, ADR candidates, issue creation |
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.
- 7d ago First seen · 115 lines · 0 tokens per session scan A 53573e2bebfd
analyze is a command published in the GitHub repository freegyes/project-ContemPlace (3 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,559 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 commands, from other repositories
sprint-status
A command that shows a project's current development status, including branches, unfinished work, local changes, stashed files, specification changes, and recent CI/CD results.
retro
A command that reviews a recent development sprint, a short period of planned work, using repository history and development metrics.
triage
Triage and categorize findings for the CLI todo system.
resolve_todo_parallel
Resolve all pending CLI todos using parallel processing.
ship-feature
Close out an in-progress feature — verify-done + brain ship (flip + checkpoint + brain check) + update feature MD + close run note.
template
Manage issue templates for streamlined issue creation.