Borrowing it
Nothing to install: this file belongs to saski/arnesto. 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/saski/arnesto/main/.agents/skills/project-status-maintenance/SKILL.mdgit clone --depth 1 https://github.com/saski/arnestoWrote 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/skills/saski/arnesto/project-status-maintenance)<a href="https://agentmods.dev/skills/saski/arnesto/project-status-maintenance"><img src="https://agentmods.dev/badge/skills/saski/arnesto/project-status-maintenance.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.00084 | $0.00761 |
| Opus 5 | $0.00042 | $0.00380 |
| Sonnet 5 | $0.00017 | $0.00152 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
project-status-maintenance 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 3d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status Maintenance
Every active project repository should maintain a PROJECT_STATUS.md at the root level. It is a living document tracking current state, completed work, and next steps.
When to update
Update PROJECT_STATUS.md after any significant change: new features, bug fixes, tests added, dependencies changed, documentation modified, project structure changes. Do not let it drift — outdated status files are worse than no file.
Canonical template
Use this structure when creating or rewriting PROJECT_STATUS.md:
# [Project Name] - Project Status
**Last Updated**: YYYY-MM-DD
**Overall Status**: [Status Emoji] **[Percentage]% Complete** - [Brief Status]
---
## Executive Summary
| Component | Status | Progress | Blocking |
|-----------|--------|----------|----------|
| Component 1 | ✅ Complete | 100% | - |
| Component 2 | 🟡 In Progress | 50% | - |
| Component 3 | ⚠️ Pending | 0% | No |
**Current Readiness**: [Status] - [Brief description]
---
## ✅ Completed Components
[List of completed work with dates and details]
---
## 🚧 In Progress
[Current work items with progress indicators]
---
## 📋 Next Steps
1. [First priority task]
2. [Second priority task]
3. [Third priority task]
---
## 🐛 Known Issues
[Any known bugs or limitations]
---
## 📝 Notes
[Additional context, decisions, or important information]
Status indicators
Use consistent indicators across the file:
- ✅ Complete — finished and tested
- 🟡 In Progress — actively being worked on
- ⚠️ Pending — planned but not started
- 🟢 Ready — ready for next phase
- 🔴 Blocked — blocked by dependencies or issues
- ❌ Cancelled — planned but cancelled
Update process
- Update the Last Updated date.
- Refresh the Overall Status percentage and brief description.
- Move items from In Progress to Completed Components when done.
- Update progress percentages for in-progress work.
- Revise Next Steps based on current priorities.
- Add any new issues to Known Issues.
- Document significant decisions in Notes.
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.
- 3d ago First seen · 111 lines · 84 tokens per session scan A 3e283a1ecd64
project-status-maintenance is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 84 tokens to every session and 761 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
flowai-live-dashboard-template
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity sparklines, and a top-contributors panel, all in a single self-contained HTML file with light/dark theming, hoverable…
code-import
Read an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.
team-okrs
OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".
huashu-keynote-black
OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.