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 CodeInfinity1/Stram --skill status-update-writinggit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/status-update-writing)<a href="https://agentmods.dev/skills/codeinfinity1/stram/status-update-writing"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/status-update-writing/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/codeinfinity1/stram/status-update-writing"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/status-update-writing.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.00031 | $0.00537 |
| Opus 5.5 | $0.00012 | $0.00215 |
| Sonnet 5.5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
status-update-writing 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Update Writing
Purpose
Turn work state into compact updates the user and collaborators can scan quickly. The preferred shape is blocker-first, evidence-backed, and clear about what is done, pending, blocked, and next.
When To Use
Use when the user asks for current status, daily update, project update, standup note, handoff, "what changed", "where are we", or a communication-ready progress summary.
Inputs And Evidence
- Git status, run results, tests, outbox, commitments, notes, and task records.
- User's target audience and channel.
- Known blockers, approvals, missing setup, or uncertainty.
Tool Map
writing_draft_createwriting_draft_inspectcognitive_statecognitive_commitment_statuscognitive_interaction_reviewread_filesearch_workspacechannel_message_preparewrite_note
Workflow
- Gather current evidence before summarizing.
- Lead with blockers or risks when they affect action.
- List completed work only when verified by files, tests, commits, or tool results.
- Separate "done", "in progress", "blocked", "not started", and "next".
- Keep updates short unless the user asks for detailed audit.
- Save status drafts with
writing_draft_createwhen the update should be reused or sent later. - Prepare channel-ready versions only after checking audience and approval needs.
Native Implementation Boundaries
- Use Stram state, file, channel, and cognition tools.
- Do not rely on upstream status templates as runtime dependencies.
- Do not use keyword matching to decide which updates matter; let model-led review rank relevance from evidence.
Safety And Approval
- Do not claim completion without verification.
- Do not expose private local paths or secrets in team updates unless necessary and approved.
- Mark uncertainty plainly.
Verification
- Each status claim should have a file, test, run, commit, or state record behind it.
- Channel drafts should be in outbox or clearly unsent.
- If evidence is missing, say what was not verified.
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 · 72 lines · 31 tokens per session scan A f1d79b451369
status-update-writing is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 537 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-09-03.
Other skills, from other repositories
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
product-management
Product management expertise for product strategy, roadmap planning, feature prioritization (RICE, ICE, MoSCoW), customer research, A/B testing, product analytics, and product-market fit. Use when building product roadmaps, prioritizing features, or defining product strategy.
init-project
Bootstrap a new research project. Interview for details, scaffold directory structure, create Overleaf symlink, initialise git, and create project context files.
shared-monorepo-turborepo
Turborepo, workspaces, package architecture, @repo/ naming, exports, tree-shaking.
setup
Interactive onboarding that discovers team structure, terminology, development goals, performance and management frameworks, organizational values, and ways of working by crawling Slack, Notion, Google Drive, Gmail, and Calendar. Validates everything with the manager before persisting. Run this first before using any…
workspace
Scaffold and manage the stateless AI workspace — context, packs, repos, and knowledge for multi-repo orchestration.