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 WellApp-ai/Well --skill session-statusgit clone --depth 1 https://github.com/WellApp-ai/WellWrote 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/wellapp-ai/well/session-status)<a href="https://agentmods.dev/skills/wellapp-ai/well/session-status"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/session-status/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/wellapp-ai/well/session-status"><img src="https://agentmods.dev/badge/skills/wellapp-ai/well/session-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.01230 |
| Opus 5.5 | $0.00006 | $0.00492 |
| Sonnet 5.5 | $0.00003 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
session-status 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 1mo 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Status Skill
Generate consistent navigation breadcrumbs showing current position, takt time, and session metrics.
When to Use
- At START of every Ask/Agent/Plan mode response
- At END of every Ask/Agent/Plan mode response
- When session metrics are needed for Session Journal sync
Phase 1: Gather State
Collect current session state:
| Data | Source |
|---|---|
| Feature name | From init context or branch name |
| Current phase | DIVERGE / CONVERGE / DEFINE / AGENT |
| Loop count | Incremented on each user feedback cycle |
| Progress | Validated items / total items |
| Duration | Time since phase started |
| Status | G (flow) / Y (waiting) / R (stopped) |
Phase 2: Calculate Takt
Compare duration against targets from 03-shared.mdc:
| Phase | Target | Warning | Stop |
|---|---|---|---|
| DIVERGE (per loop) | 15min | 30min | 60min |
| CONVERGE | 20min | 40min | 90min |
| DEFINE | 10min | 20min | 45min |
| Commit (each) | 10min | 20min | 30min |
Determine suffix:
- Under target: (none)
- Warning exceeded:
! - Stop exceeded:
!!
Phase 3: Format Header
Generate single-line breadcrumb:
Format: [STATUS] | [Feature] | [PHASE_PROGRESS] | L[N] | [X]/[Y] | [TIME]
Examples by phase:
- DIVERGE:
G | Collaboration | DIVERGE ###....... | L3 | 5/9 | 18m - CONVERGE:
G | Collaboration | DIVERGE OK | CONVERGE ##.... | L1 | 22m - DEFINE:
G | Collaboration | DIVERGE OK | CONVERGE OK | DEFINE ###.. | L2 | 35m - AGENT:
G | Collaboration | AGENT | C2/5 | 45m - Warning:
Y | Collaboration | DIVERGE ###....... | L3 | 5/9 | 32m! - Stopped:
R | Collaboration | AGENT | JIDOKA STOP
Progress bar: 10 chars, # filled, . empty, proportional to completion.
Phase 4: Format Footer
Generate context-specific footer:
---
Next: [action prompt]
Dynamic prompts by context:
| Context | Footer Prompt |
|---|---|
| DIVERGE with DIG | Provide OK/KO/DIG for: #4, #6, #7 |
| Gate 1 passed | All validated. Say "converge" to proceed. |
| Gate 2 | Choose option: A / B / C |
| Gate 3 | Approve phasing: OK / REORDER / SPLIT |
| AGENT | Commit 2/5 in progress... |
| Jidoka stop | Reply with A, B, C, or D |
| Autonomous | Iteration 3/5... |
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.
- 1mo ago First seen · 181 lines · 16 tokens per session scan A 53988e1b8342
session-status is a skill published in the GitHub repository WellApp-ai/Well (345 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 1,230 once invoked, about $0.0001 per session on Opus 5.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
a0-development
Develop or operate Agent Zero: projects, chats, tasks, framework, tools and API/WebUI.
meeting-transcript-to-action-items
Listen to a meeting recording and extract structured action items, decisions, and open questions. Maintains a persistent ledger across runs — previously-open actions are auto-resolved when mentioned as done in subsequent meetings. Outputs actions.csv (importable to Linear/Asana/Notion) + recap.md (paste into Slack).…
feishu-openapi-skill
Operate Feishu or Lark IM APIs through UXC with a curated OpenAPI schema, tenant-token bearer auth, and chat/message guardrails.
slack-openapi-skill
Operate Slack Web API through UXC with a curated OpenAPI schema, bearer-token auth, and messaging-core guardrails.
zapier-patterns
Use when zapier automation patterns — triggers, actions, filters, formatters, paths, code steps. Use when working with zapier patterns.
flowise-builder
Use when flowise visual LLM workflow builder — drag-drop chatflows, API endpoints, document loaders, tools. Use when working with flowise builder.