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/griddynamics/rosetta/daily-ossnpx skills add griddynamics/rosetta --skill daily-ossgit 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.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.00017 | $0.01888 |
| Opus 5 | $0.00009 | $0.00944 |
| Sonnet 5 | $0.00003 | $0.00378 |
| Haiku 4.5 | $0.00002 | $0.00189 |
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 4d 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 — 78 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.
- 4d ago First seen · 78 lines · 17 tokens per session scan A 53a2e5342036
daily-oss is a skill published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 1,888 once invoked, about $0.0001 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
azure-devops-rest-api
Guide for working with Azure DevOps REST APIs and OpenAPI specifications. Use this skill when implementing new Azure DevOps API integrations, exploring API capabilities, understanding request/response formats, or referencing the official OpenAPI specifications from the vsts-rest-api-specs repository.
decision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.