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 skills/posit-dev/skills/working-onnpx skills add posit-dev/skills --skill working-ongit clone --depth 1 https://github.com/posit-dev/skillsWrote 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/posit-dev/skills/working-on)<a href="https://agentmods.dev/skills/posit-dev/skills/working-on"><img src="https://agentmods.dev/badge/skills/posit-dev/skills/working-on.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 | $0.00056 | $0.00442 |
| Opus 5 | $0.00028 | $0.00221 |
| Sonnet 5 | $0.00011 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
working-on 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.
What it actually says
Working On
You are managing a tracking document that serves as the source of truth for the current task or feature.
The tracking document is: $path
Behavior
Once activated, treat the tracking document as a living record. Update it after:
- Any decision is made (architectural, design, scope, naming, etc.)
- A new problem, bug, or edge case is discovered
- A new sub-feature or requirement emerges
- An issue is raised or resolved
- Any significant implementation work is completed
- A key part of a conversation with the user that would be useful to recall later
- Any time you commit files — a commit is a strong signal that the tracking document should also be reviewed and updated
- Any plan you form — write it to the document rather than presenting it only in chat; the document is the persistent record
If in doubt, update the document. It is better to over-document than to lose context.
Git Handling
Do NOT commit the tracking document unless it already appears in the repository's git history. If the file is not tracked by git, leave it out of any commits.
Guidelines
- Keep updates concise — bullet points and short paragraphs are preferred over prose
- Use timestamps or date headers when the document spans multiple sessions
- Record the why behind decisions, not just the what
- When a section becomes stale or irrelevant, move it to an "Archive" or "Resolved" section rather than deleting it
- If the document doesn't exist yet, create it with a sensible structure based on the task at hand
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 · 45 lines · 56 tokens per session scan A 5b3ad75cb856
working-on is a skill published in the GitHub repository posit-dev/skills (488 stars, last pushed 6d ago), licensed MIT. It adds 56 tokens to every session and 442 once invoked, about $0.0003 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
docx-comment-reply
Reply to comments (批注) in Word .docx/.doc files: extract comment context, draft replies, write threaded replies back, and validate OOXML.
file-forensics
Examine what a file claims about itself and what it actually contains — powered by Apache Tika. True content-based type detection (extensions lie), provenance claims (authors, dates, creating application), revision and tamper signals (PDF incremental updates, tracked changes, hidden slides, zip integrity), hidden and…