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 tms-tungnguyen3/daily_working --skill daily-workinggit clone --depth 1 https://github.com/tms-tungnguyen3/daily_workingWrote 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/tms-tungnguyen3/daily_working/daily-working)<a href="https://agentmods.dev/skills/tms-tungnguyen3/daily_working/daily-working"><img src="https://agentmods.dev/badge/skills/tms-tungnguyen3/daily_working/daily-working/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/tms-tungnguyen3/daily_working/daily-working"><img src="https://agentmods.dev/badge/skills/tms-tungnguyen3/daily_working/daily-working.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.00098 | $0.01644 |
| Opus 5.5 | $0.00039 | $0.00658 |
| Sonnet 5.5 | $0.00020 | $0.00329 |
| Haiku 4.5 | $0.00010 | $0.00164 |
Grade A, and why
daily-working 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
daily-working
Purpose
Coordinate a full task-to-verified-change loop without the human relaying context by hand: fetch a task from the project's task tracker (with attachments), judge whether it's actually safe and sensible to implement as understood, implement it following the target project's own conventions, verify the result in a real running browser, and close the loop back on the tracker (PR + comment + status) once that's confirmed.
Task tracker support today: Redmine and GitHub Issues. task_tracker in .claude/daily-working.yml picks one; the pipeline itself (phases/fetch-task, phases/close, templates/tracker-write) only ever calls a small fixed contract — fetch, write_comment, set_status — defined in policies/tracker-adapter. Each tracker's actual mechanics live in their own adapters/<name>.md file. Adding a third tracker means writing one new adapter file; nothing under phases/, workflows/, or templates/ needs to change.
If a requirement turns out ambiguous, unreasonable, or too high-impact to proceed on quietly at any point, that gets escalated to a comment on the tracker (not just asked in this chat) and the pipeline pauses — see policies/safety.
This skill is a coordinator — it does not replace the target project's own test conventions. It sequences task tracker → implementation → live browser check → tracker update.
When to Use
- User gives a task/ticket ID from the project's tracker (e.g.
#4626, or a ticket key likePROJ-4626if this project's commits use one) and asks to implement it - User says "lấy task từ redmine", "làm task này", "pull the ticket and implement it"
- User asks to verify/review an already-implemented change against a ticket
- User asks to resume a ticket that was previously paused on an open question
- Any request that should end with a live UI check, not just passing tests
What ships with it
21 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- adapters/github.md 4.5 KB
- adapters/redmine.md 5.1 KB
- phases/assess.md 3.0 KB
- phases/close.md 2.3 KB
- phases/fetch-task.md 4.3 KB
- phases/implement.md 3.1 KB
- phases/setup.md 6.2 KB
- phases/test.md 990 B
- phases/verify.md 1.1 KB
- policies/browser.md 3.1 KB
- policies/database.md 1.9 KB
- policies/git.md 1.5 KB
- policies/parallel.md 9.0 KB
- policies/safety.md 3.4 KB
- policies/tracker-adapter.md 4.0 KB
- templates/pr.md 1.6 KB
- templates/summary.md 613 B
- templates/tracker-write.md 1.9 KB
- workflows/implement.md 2.3 KB
- workflows/resume.md 2.1 KB
- workflows/review.md 1.9 KB
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 Changed · +2 lines 254243194866
- 1mo ago Changed a6574b6cc8b3
- 1mo ago Changed · -255 lines · +17 tokens per session scan D → A 07719846974b
- 1mo ago First seen · 335 lines · 81 tokens per session scan D 50424ea930e9
daily-working is a skill published in the GitHub repository tms-tungnguyen3/daily_working (5 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 1,644 once invoked, about $0.0004 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-31.
Other skills, from other repositories
fleet-retrofit
Bulk remediation across the fleet registry: fix drift repo-by-repo and optionally bootstrap the un-governed ones — every repo previewed and confirmed individually. TRIGGER when the user says "fix drift across all my repos", "retrofit the fleet", "retrofit all my repos", "bring every repo into compliance", "remediate…
learn-profile
Inspect a reference repo and save its nyann-relevant setup (stack, hooks, branching, commit convention, extras) as a reusable profile. TRIGGER when the user says "save this setup as a profile called X", "learn a profile from /projects/foo", "capture this repo's setup as my-profile", "make a profile from this repo"…
sync-team-profiles
Fetch (or refresh) registered team-profile sources — git clone on first run, shallow git fetch + reset on subsequent runs — and register discovered profiles under a namespace. TRIGGER when the user says "sync team profiles", "pull the latest team profiles", "refresh team profiles", "update team profiles", "sync from…
inspect-profile
Explain in plain English what a nyann profile enables — stack, branching, hooks, extras, conventions, documentation. TRIGGER when the user says "what does the nextjs-prototype profile do", "explain the python-cli profile", "show me what enables", "what's in profile X", "describe the profile", "inspect profile X"…
migrate-profile
Switch this repository from one nyann profile to another. TRIGGER ON: 'switch profile', 'migrate profile', 'change this repo profile', 'switch from X to Y', 'change profile to', 'migrate from', 'use a different profile', 'switch to nextjs', 'switch to python'. Computes a diff between source and target profiles…
gen-templates
Generate GitHub PR and issue templates for this repository. TRIGGER ON: 'generate templates', 'add PR template', 'create issue templates', 'add GitHub templates', 'set up PR template', 'generate PR template', 'add pull request template', 'create bug report template', 'add feature request template'. Generates…