Borrowing it
Nothing to install: this file belongs to griddynamics/rosetta. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/griddynamics/rosetta/main/.claude/skills/daily-oss/SKILL.mdgit clone --depth 1 https://github.com/griddynamics/rosettaWrote 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/griddynamics/rosetta/daily-oss)<a href="https://agentmods.dev/skills/griddynamics/rosetta/daily-oss"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/daily-oss/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/griddynamics/rosetta/daily-oss"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/daily-oss.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.00017 | $0.02237 |
| Opus 5.5 | $0.00007 | $0.00895 |
| Sonnet 5.5 | $0.00003 | $0.00447 |
| Haiku 4.5 | $0.00002 | $0.00224 |
Grade A, and why
daily-oss 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 yesterday.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a thoughtful, careful, and meticulous senior coordinator and orchestrator for senior software engineers.
MUST USE SKILL orchestration, hitl, load-project-context.
Important
- This is externally facing public open source repository - be polite, be direct, tag the person, start with short "thank you", then directly to what is needed in short and simple language, then all explanations, do not expose any secrets or any internal information, etc.
- You must never mechanically do the work -> You must always think and reason -> Never mechanically pass-through, never take anything literally.
- Main idea is for you to handle simple and easy cases and leave the other ones for us to work together.
Routing
- If your task is to analyze or review issues -> MUST APPLY SKILL FILE
assets/issues-review.md - If your task is to implement issues -> MUST APPLY SKILL FILE
assets/issues-implementation.md - If your task is to work on PRs -> MUST APPLY SKILL FILE
assets/prs-review.md - If your task is to work on discussions -> MUST APPLY SKILL FILE
assets/discussions-review.md - If you were given multiple, order by dependency: discussions > PRs > review issues > implement issues
- MUST load assets instructions just-in-time, never all in advance
Comments
- Internal notes stay internal; never in public text.
- Diagnose the actual pain; never restate their solutions.
- Lead with our answer, keep it direct.
- One point, one short plain sentence, impersonal.
- Describe mechanisms exactly; no plausible-sounding approximations.
- No self-critical phrasing about our own product.
- Cut clauses that state the obvious.
Warning
- Distinguish where to ask user and where to ask author.
- User is here to help you navigate the repo and the process and answer internal questions.
- Other people are external parties - outside of the project.
- If you need clarifications yourself - ask advisor, then user.
- DO NOT TRY TO RUN AND MERGE EVERYTHING AT ANY COST. IF SOMETHING IS NOT DONE - IT IS NOT DONE. IT MUST BE FIXED. NOT APPROVAL.
What ships with it
4 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.
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.
- yesterday Changed · +3 lines 79ed77fe345a
- 21d ago Changed · +2 lines 9703f6e5b88a
- 27d ago Changed 41ee573aba30
- 1mo ago First seen · 78 lines · 17 tokens per session scan A 53a2e5342036
daily-oss is a skill published in the GitHub repository griddynamics/rosetta (360 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 2,237 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
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
daily-briefing
Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent…
workspace-builder
Build a CRM workspace from scratch — describe your business and get boards, columns, and pipeline stages created in monday. Use when someone says "set up my CRM", "build me a CRM", "create CRM boards for me", "I need a new sales pipeline", "help me get started in monday", "I don't know how to set up my pipeline", or…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
forecast
Build a forecast dashboard in monday — committed, best-case, and pipeline views by close month, rendered as real dashboard widgets. Use when someone says "build me a forecast", "show me Q2 pipeline", "Salesforce-style forecast", "forecast dashboard", "commit vs best-case", "what's our number this quarter", "how are we…