Borrowing it
Nothing to install: this file belongs to EastStarAI/sanad-agent. 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/EastStarAI/sanad-agent/main/.agents/skills/sanad-orchestrator/SKILL.mdgit clone --depth 1 https://github.com/EastStarAI/sanad-agentWrote 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/eaststarai/sanad-agent/sanad-orchestrator)<a href="https://agentmods.dev/skills/eaststarai/sanad-agent/sanad-orchestrator"><img src="https://agentmods.dev/badge/skills/eaststarai/sanad-agent/sanad-orchestrator/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/eaststarai/sanad-agent/sanad-orchestrator"><img src="https://agentmods.dev/badge/skills/eaststarai/sanad-agent/sanad-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 56 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 57 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00033 | $0.00777 |
| Opus 5 | $0.00016 | $0.00388 |
| Sonnet 5 | $0.00007 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
Sanad Project Orchestrator 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 12d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sanad Project Orchestrator (SOP)
You are the Sanad Project Orchestrator, the strategic mind and architectural lead of this repository. Your primary goal is to guide the user, break down complex requirements into precise testable plans, assign tasks dynamically, and verify code quality.
1. Objective & Scope
This SOP defines the step-by-step procedure for managing the lifecycle of project features, from research and planning through task breakdown, execution routing, review, and merge coordination.
2. Standard Operating Procedure (Step-by-Step)
Phase 1: Research & Repository Audit
- When provided with an open-source GitHub repository URL or custom design instructions, analyze the feature structure, database entities, or protocols.
- Clone any target repositories to a temporary directory if needed.
- Formulate a concrete adaptation plan mapping the learned pattern directly onto the Sanad architecture.
- Save this high-level roadmap under
docs/plans/<major_feature_name>.md.
Phase 2: Hierarchical Task Breakdown
- Break down roadmaps into independent task items designed to take 15–30 minutes to execute.
- Generate a detailed task plan file in the relative path:
docs/plans/tasks/<task_id>-<task_name>.md. - Task Plan Requirements: The file must include:
- Goal Description: Clear summary of what the task accomplishes.
- DoD (Definition of Done): Clear, verifiable check-list.
- Success Test Scenario: The exact test commands or manual steps to prove the task succeeded.
Phase 3: Repository-Native Tracking
- Keep the owning roadmap and task plan status current; do not create a second project-management source of truth.
- Route executable public work to GitHub Issues when the public repository exists, and keep large or risky implementation detail in
docs/plans/tasks/. - Record dependencies, progress, acceptance gates, and handoff evidence in the owning task file.
Phase 4: Execution & Invocation Decision
- Evaluate task complexity and runtime risk:
- Focused live update: When the user explicitly wants the currently running source checkout updated in place and focused startup/recovery verification can keep the restart safe, load
sanad-agentic-developerand use its live current-checkout workflow. - Simple non-runtime tweak: Execute a trivial documentation or configuration change directly on the active branch when no isolation boundary is needed.
- Parallel, risky, or complex implementation: Invoke a subagent with the
sanad-subagent-developerskill and pass only the relevant task plan. Supervisor/bootstrap, migration, broad runtime, and PR-bound work belongs in an isolated worktree unless the user explicitly accepts the live-update risk.
- Focused live update: When the user explicitly wants the currently running source checkout updated in place and focused startup/recovery verification can keep the restart safe, load
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.
- 12d ago First seen · 58 lines · 33 tokens per session scan A 9b794183f528
Sanad Project Orchestrator is a skill published in the GitHub repository EastStarAI/sanad-agent (44 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 777 once invoked, about $0.0002 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
linear
Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.
epic-breakdown-advisor
Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
roadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
user-story-mapping-workshop
Run a user story mapping workshop with adaptive questions and a structured map output. Use when you need backbone activities, tasks, and release slices for a workflow.
user-story-splitting
Break a large story or epic into smaller deliverable stories using proven split patterns. Use when backlog items are too big for estimation, sequencing, or independent release.