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 skills add dungnotnull/hybrid-harness-chaos-process-prm --skill s03-progress-trackergit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s03-progress-tracker)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s03-progress-tracker"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s03-progress-tracker/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/skills/dungnotnull/hybrid-harness-chaos-process-prm/s03-progress-tracker"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s03-progress-tracker.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.00099 | $0.03948 |
| Opus 5 | $0.00049 | $0.01974 |
| Sonnet 5 | $0.00020 | $0.00790 |
| Haiku 4.5 | $0.00010 | $0.00395 |
Grade A, and why
progress-tracker 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 12d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Progress Tracker (s03)
Purpose
Maintain a single source of truth for workflow progress across all phases and agent sessions. Prevent duplicated work, track blockers, surface missed tasks, and provide clear status visibility — ensuring work consistency even when switching between AI agents or resuming after interruptions.
Prerequisites
- Orchestrator (s00) has been loaded for context
- .commandcode/ directory exists for state persistence
- No specific skill outputs required — this skill initializes state
Input Contract
| Input | Source | Required |
|---|---|---|
| Orchestrator dispatch events | s00 workflow_context | Yes |
| Skill completion signals | Each skill's output | Yes |
| Previous progress state | .commandcode/progress.json |
No (created if absent) |
| Blocker reports | Any skill encountering issues | No |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Updated progress.json | .commandcode/progress.json |
JSON |
| Workflow dashboard | Terminal output | Colored Markdown |
| Burndown data | Progress JSON (embedded) | JSON |
| Missed task alerts | User + orchestrator | Text |
| Agent handoff summary | Next agent session | Markdown |
Progress State Schema
{
"project": "hybrid-harness-chaos-process-prm",
"workflow_version": "1.0",
"created_at": "2025-01-15T10:00:00Z",
"updated_at": "2025-01-15T16:30:00Z",
"total_phases": 26,
"completed_phases": 12,
"current_phase": "13-hypothesis-validation",
"agent": "claude-code-3.5",
"phases": {
"00-orchestrator": {
"status": "completed",
"started_at": "2025-01-15T10:00:00Z",
"completed_at": "2025-01-15T10:02:00Z",
"agent": "claude-code-3.5",
"artifacts": ["progress.json created"],
"notes": ""
},
"01-ba-requirements": {
"status": "completed",
"started_at": "2025-01-15T10:02:00Z",
"completed_at": "2025-01-15T11:45:00Z",
"agent": "claude-code-3.5",
"artifacts": ["prd.md", "adr/adr-001-kubernetes-deployment.md", "backlog.md"],
"notes": "PRD approved by engineering lead"
},
"02-taste-memory": {
"status": "completed",
"started_at": "2025-01-15T10:00:00Z",
"completed_at": "2025-01-15T10:01:00Z",
"agent": "system",
"artifacts": [],
"notes": "Loaded 23 taste preferences"
},
"03-progress-tracker": {
"status": "completed",
"started_at": "2025-01-15T10:00:00Z",
"completed_at": "2025-01-15T10:02:00Z",
"agent": "system",
"artifacts": [],
"notes": "Initialized"
},
"04-pipeline-design": {
"status": "completed",
"started_at": "2025-01-15T11:45:00Z",
"completed_at": "2025-01-15T14:20:00Z",
"agent": "claude-code-3.5",
"artifacts": ["pipeline-payment-service.yaml", "trigger-config.yaml"],
"notes": "Pipeline generated with chaos step placeholder"
},
"05-service-onboarding": {
"status": "completed",
"started_at": "2025-01-15T14:20:00Z",
"completed_at": "2025-01-15T15:30:00Z",
"agent": "claude-code-3.5",
"artifacts": ["service-payment.yaml", "env-dev.yaml", "env-staging.yaml", "infra-def.yaml"],
"notes": ""
},
"06-delegate-management": {
"status": "completed",
"started_at": "2025-01-15T15:30:00Z",
"completed_at": "2025-01-15T15:50:00Z",
"agent": "claude-code-3.5",
"artifacts": ["delegate-helm-values.yaml", "delegate-rbac.yaml"],
"notes": ""
},
"07-secrets-management": {
"status": "completed",
"started_at": "2025-01-15T15:50:00Z",
"completed_at": "2025-01-15T16:00:00Z",
"agent": "claude-code-3.5",
"artifacts": ["vault-connector.yaml", "secret-references.yaml"],
"notes": "Using Vault with K8s auth"
},
"08-feature-flags": {
"status": "completed",
"started_at": "2025-01-15T16:00:00Z",
"completed_at": "2025-01-15T16:10:00Z",
"agent": "claude-code-3.5",
"artifacts": ["ff-payment-new-checkout.yaml", "ff-chaos-payment.yaml"],
"notes": "Chaos kill switch FF created"
},
"09-template-library": {
"status": "completed",
"started_at": "2025-01-15T16:10:00Z",
"completed_at": "2025-01-15T16:15:00Z",
"agent": "claude-code-3.5",
"artifacts": ["template-standard-deploy.yaml", "template-security-scan.yaml"],
"notes": ""
},
"10-gitops": {
"status": "completed",
"started_at": "2025-01-15T16:15:00Z",
"completed_at": "2025-01-15T16:25:00Z",
"agent": "claude-code-3.5",
"artifacts": ["app-payment-production.yaml", "applicationset.yaml"],
"notes": ""
},
"11-cloakbrowser-testing": {
"status": "completed",
"started_at": "2025-01-15T16:25:00Z",
"completed_at": "2025-01-16T09:00:00Z",
"agent": "claude-code-3.5",
"artifacts": ["test-results.xml", "coverage-report.html"],
"notes": "All tests passing, 85% coverage"
},
"12-experiment-design": {
"status": "completed",
"started_at": "2025-01-16T09:00:00Z",
"completed_at": "2025-01-16T09:45:00Z",
"agent": "claude-code-3.5",
"artifacts": ["experiment-pod-delete.yaml", "engine-payment-pod-delete.yaml"],
"notes": ""
},
"13-hypothesis-validation": {
"status": "in_progress",
"started_at": "2025-01-16T09:45:00Z",
"completed_at": null,
"agent": "claude-code-3.5",
"artifacts": [],
"notes": "Hypothesis written for pod-delete, validating acceptance criteria"
},
"14-blast-radius-control": { "status": "pending" },
"15-steady-state": { "status": "pending" },
"16-infrastructure-faults": { "status": "pending" },
"17-application-faults": { "status": "pending" },
"18-game-day-planning": { "status": "pending" },
"19-cv-verification": { "status": "pending" },
"20-observability-integration": { "status": "pending" },
"21-alerting-recommendations": { "status": "pending" },
"22-policy-governance": { "status": "pending" },
"23-cloud-cost-management": { "status": "pending" },
"24-resilience-scoring": { "status": "pending" },
"25-postmortem-learning": { "status": "pending" }
},
"blockers": [],
"metrics": {
"estimated_total_hours": 40,
"elapsed_hours": 6.5,
"velocity_phases_per_hour": 1.85,
"estimated_completion": "2025-01-18T14:00:00Z"
}
}
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.
- 12d ago First seen · 439 lines · 99 tokens per session scan A 27f867727848
progress-tracker is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 99 tokens to every session and 3,948 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.