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 rules/rizkyhaksono/portfolio-v3/project-managementgit clone --depth 1 https://github.com/rizkyhaksono/portfolio-v3Wrote 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/rules/rizkyhaksono/portfolio-v3/project-management)<a href="https://agentmods.dev/rules/rizkyhaksono/portfolio-v3/project-management"><img src="https://agentmods.dev/badge/rules/rizkyhaksono/portfolio-v3/project-management.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.00326 | $0.00326 |
| Opus 5 | $0.00163 | $0.00163 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
project-management 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 6d 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.
This is a copy
100% identical to project-mangement — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Rules File: Progress Tracking System
Core Rules
-
Always read feature.md first
- Read and understand the complete feature requirements
- Identify all tasks and deliverables outlined in feature.md
- Use this as the source of truth for what needs to be accomplished
-
Always read progress.md before starting work
- Check current status of all tasks
- Identify what has been completed
- Identify what remains to be done
- Avoid duplicating completed work
-
Update progress.md after completing any task
- Mark completed tasks with status and timestamp
- Add detailed notes about what was accomplished
- Update percentage completion if applicable
- Note any blockers or issues encountered
-
Progress.md Structure Requirements
- Maintain clear task breakdown from feature.md
- Use consistent status indicators (TODO, IN_PROGRESS, COMPLETED)
- Include timestamps for all status changes
- Provide brief descriptions of work completed
- Track overall feature completion percentage
-
Task Completion Workflow
- Read feature.md → Read progress.md → Complete task → Update progress.md
- Never skip the progress update step
- Be specific about what was accomplished in each update
- Reference specific files, functions, or components modified
-
Quality Standards
- Ensure progress updates are accurate and detailed
- Maintain chronological order of updates
- Keep progress.md synchronized with actual work completed
- Use clear, professional language in all updates
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.
- 6d ago First seen · 44 lines · 326 tokens per session scan A e0b2b1773f1a
project-management is a cursor rule published in the GitHub repository rizkyhaksono/portfolio-v3 (6 stars, last pushed 8d ago), licensed MIT. It adds 326 tokens to every session, about $0.0016 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to project-mangement, differing in 1 line, and is treated as a copy.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制,1小时超时.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).