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 commands/peakflames/polarionmcpservers/incremental-implementationgit clone --depth 1 https://github.com/peakflames/PolarionMcpServersWrote 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/peakflames/polarionmcpservers/incremental-implementation)<a href="https://agentmods.dev/commands/peakflames/polarionmcpservers/incremental-implementation"><img src="https://agentmods.dev/badge/commands/peakflames/polarionmcpservers/incremental-implementation.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 | $0.00000 | $0.05140 |
| Opus 5 | $0.00000 | $0.02570 |
| Sonnet 5 | $0.00000 | $0.01028 |
| Haiku 4.5 | $0.00000 | $0.00514 |
Grade A, and why
incremental-implementation 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 4d 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 — 823 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incremental Phase Implementation Workflow
No Task Specified Protocol
<no_task_protocol> When the user does not specify a task (e.g., empty message, "continue", "what's next?"), Claude must proactively assess the project state and propose next steps.
Step 1: Assess Current State
-
Check Git Status
git status && git branch -a && git --no-pager log --oneline -10 -
Identify Current Phase and Version
- Read
CHANGELOG.mdfor current version - Check recent commits for current work context
- Read
-
Check for Existing Implementation Plans
- Look for
docs/plans/ortmp/for implementation plans - Identify current task status
- Look for
-
Check for Incomplete Work
- Review any verification checklists in
docs/verification/ - Check for uncommitted changes or unmerged feature branches
- Review any verification checklists in
Step 2: Determine Next Action
Based on the assessment, recommend ONE of the following:
| State | Recommended Action |
|---|---|
| Uncommitted changes exist | Complete current work, commit, await approval |
| Feature branch exists but not merged | Complete task, await approval for merge |
| Phase plan exists with incomplete tasks | Propose starting next task |
| Current phase complete, no next phase plan | Propose creating next phase implementation plan |
| All phases complete | Propose maintenance, enhancements, or new phase planning |
Step 3: Present Proposal to User
Format the proposal clearly:
## Project State Assessment
**Current Version:** {version}
**Current Branch:** {branch}
**Last Commit:** {hash} - {message}
## Recommendation
{One of the following:}
**Option A: Continue Current Work**
- Task: {task description}
- Status: {status}
- Next Steps: {specific steps}
**Option B: Start New Task**
- Phase {N} Task {M}: {title}
- Dependencies: {met/unmet}
- Estimated effort: {S/M/L}
**Option C: Create Phase {N+1} Implementation Plan**
- Current phase status: Complete
- Suggested next phase focus: {area}
- Would you like me to draft the implementation plan?
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.
- 4d ago First seen · 823 lines · 0 tokens per session scan A bf41c84a6234
incremental-implementation is a command published in the GitHub repository peakflames/PolarionMcpServers (38 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,140 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.