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 tahirraufkeeyu/software-development-agent-stack--sdas --skill onboarding-guidegit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/onboarding-guide)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/onboarding-guide"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/onboarding-guide/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/tahirraufkeeyu/software-development-agent-stack--sdas/onboarding-guide"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/onboarding-guide.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.00073 | $0.02744 |
| Opus 5 | $0.00036 | $0.01372 |
| Sonnet 5 | $0.00015 | $0.00549 |
| Haiku 4.5 | $0.00007 | $0.00274 |
Grade A, and why
onboarding-guide 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 9d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Trigger this skill when:
- A new engineer, designer, PM, or analyst is joining a team.
- An internal transfer is moving to a team and needs a ramp plan.
- A team is reviewing its onboarding materials for staleness (quarterly refresh).
- Contractor or partner-team members need a time-bounded ramp.
Do not use this skill for:
- Company-wide onboarding (HR, benefits, org policies) — those belong in a central HR doc.
- Role-specific onboarding plans that require manager judgment (career ladder conversations, perf expectations).
Inputs
Required:
- Team name and project/repo path (local or GitHub URL).
- New hire's role (e.g., "backend engineer," "product designer").
Optional:
- New hire's start date (to anchor Week 1 and Month 1 dates).
- Manager name (for 1:1 setup pointers).
- Access systems the team uses beyond defaults (e.g., dedicated AWS account, Datadog org, staging VPN).
- Path to existing onboarding doc — the skill will refresh it rather than start from scratch.
Outputs
A Markdown document with the following sections:
- Welcome — one-paragraph intro to the team's mission.
- Day 1 — access checklist — everything needed to log in and say hi.
- Week 1 — ramp reading list + first PR target.
- Month 1 — owned areas + first on-call shadow.
- Glossary — team-specific terms, acronyms, project codenames.
- Who to ask for what — a table.
- Runbooks index — links to the team's operational runbooks.
- Feedback — how the new hire should report gaps in this doc.
Tool dependencies
- Read / Grep / Glob — scan
README.md,CONTRIBUTING.md,CODEOWNERS,.github/workflows/,docs/. - Bash —
git log --format='%aN' | sort -uto list contributors;git shortlog -snfor top contributors to suggest mentors. - GitHub MCP — list repo topics, contributors, and recent good-first-issues.
- Notion MCP (optional) — read team wiki pages (runbooks, glossary).
- Slack MCP (optional) — identify the team's working channels.
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.
- 9d ago First seen · 183 lines · 73 tokens per session scan A 0f5c2a5d03f0
onboarding-guide is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 73 tokens to every session and 2,744 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.