Borrowing it
Nothing to install: this file belongs to SAGAAIDEV/mcp-ahrefs. 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/SAGAAIDEV/mcp-ahrefs/main/.claude/commands/onboarding-workflow.mdgit clone --depth 1 https://github.com/SAGAAIDEV/mcp-ahrefsWrote 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/commands/sagaaidev/mcp-ahrefs/onboarding-workflow)<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/onboarding-workflow"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/onboarding-workflow/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/commands/sagaaidev/mcp-ahrefs/onboarding-workflow"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/onboarding-workflow.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.00017 | $0.01547 |
| Opus 5 | $0.00009 | $0.00773 |
| Sonnet 5 | $0.00003 | $0.00309 |
| Haiku 4.5 | $0.00002 | $0.00155 |
Grade A, and why
onboarding-workflow 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚀 Welcome to AI-Driven Development with Claude!
I'll guide you through our complete development workflow. This process leverages Claude Code to implement JIRA issues efficiently while maintaining code quality.
📋 Complete Workflow Overview
Here's EXACTLY what you'll do from start to finish:
-
Start JIRA Work →
/project:start-issue [ISSUE-KEY] saaga- Fetches JIRA ticket, creates branch, begins implementation
-
Guide Claude's Coding → Monitor and provide feedback
- Review changes, answer questions, course-correct as needed
-
Run Automated Tests → Have Claude run pytest/npm test
- Ensures existing functionality isn't broken
-
Generate & Launch Test MCP Server →
/project:generate-test-server- Creates fresh MCP server, launches Inspector & Admin UI for manual testing
-
Create Pull Request →
/project:complete-issue- Commits changes, pushes branch, creates PR
- YOU MUST notify team in Slack/Teams
-
Sync After PR Merged →
/project:post-merge- Updates local main with merged changes, cleans up branch
Would you like detailed information about what each command does? Let me know and I'll explain the complete process for any step.
Step 1: Start Your JIRA Issue 🎯
Begin by having Claude retrieve and analyze your assigned JIRA issue:
/project:start-issue [ISSUE-KEY] saaga
Example: /project:start-issue ASEP-42 saaga
What happens:
- Claude fetches the JIRA issue details
- Reviews the current codebase structure
- Creates a feature branch
- Forms an implementation plan
- Begins coding the solution
Your role:
- ✅ Review Claude's understanding of the issue
- ✅ Confirm the implementation plan makes sense
- ✅ Guide Claude if additional context is needed
Step 2: Monitor and Guide Implementation 👀
As Claude implements the solution:
Watch for:
- File modifications and creations
- Claude's use of the TodoWrite tool to track progress
- Any questions or clarifications Claude requests
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 · 223 lines · 17 tokens per session scan A 71a70af4afc9
onboarding-workflow is a command published in the GitHub repository SAGAAIDEV/mcp-ahrefs (0 stars, last pushed 1y ago), licensed MIT. It adds 17 tokens to every session and 1,547 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.