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 jrjsmrtn/project-orchestration-skills --skill analyze-projectgit clone --depth 1 https://github.com/jrjsmrtn/project-orchestration-skillsWrote 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/jrjsmrtn/project-orchestration-skills/analyze-project)<a href="https://agentmods.dev/skills/jrjsmrtn/project-orchestration-skills/analyze-project"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/analyze-project/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/jrjsmrtn/project-orchestration-skills/analyze-project"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/analyze-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Memory Poisoning · line 134 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00043 | $0.04928 |
| Opus 5 | $0.00022 | $0.02464 |
| Sonnet 5 | $0.00009 | $0.00986 |
| Haiku 4.5 | $0.00004 | $0.00493 |
Grade A, and why
analyze-project scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| The **security / reporting** page | curl — disclosure is mandatory for AI-found vulnerabilities | How it starts
The opening of the file, as written. The whole thing — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SPARK Analysis
Conduct SPARK methodology analysis for new project inception.
When to Use
- At the very beginning of a new project
- When evaluating a significant new feature or system
- Before running
bootstrap-projectto validate project viability - When pivoting or reassessing an existing project
What is SPARK?
SPARK is a structured inception methodology for validating project viability:
- Stakeholders: Who is affected and who has influence?
- Problem: What problem are we solving? What's the scope?
- Analysis: What exists? What are the options? What are the constraints?
- Risks: What could go wrong? How do we mitigate?
- Knowledge: What do we know? What gaps exist?
Alternative Interpretation: Some practitioners use SPARK as: Situation, Proposal, Agreement, Resources, Kickers. This variant focuses more on proposal-driven inception where the situation is assessed, a proposal is made, agreement is sought, resources are identified, and potential "kickers" (deal-breakers or critical success factors) are surfaced early. Choose the interpretation that best fits your project context.
Required Inputs
- Project idea/concept (initial description)
- Context (why now? what triggered this?)
- Initial stakeholder list (who asked for this?)
- Time constraints (deadline pressures?)
- Budget/resource constraints (if known)
Workflow
Phase 1: Stakeholder Analysis
Identify and analyze all stakeholders:
## Stakeholders
### Primary Stakeholders (Direct Users)
| Stakeholder | Role | Needs | Influence | Engagement |
|-------------|------|-------|-----------|------------|
| [Name/Role] | [What they do] | [What they need] | High/Med/Low | [How to engage] |
### Secondary Stakeholders (Indirect Impact)
| Stakeholder | Interest | Impact | Communication |
|-------------|----------|--------|---------------|
| [Name/Role] | [Their interest] | [How affected] | [How to inform] |
### Key Questions to Answer
- Who will use this system daily?
- Who will maintain/operate it?
- Who funds/sponsors it?
- Who could block or derail the project?
- Who has domain expertise we need?
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.
- 11d ago First seen · 469 lines · 43 tokens per session scan A 1513a8200fbe
analyze-project is a skill published in the GitHub repository jrjsmrtn/project-orchestration-skills (15 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 4,928 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
linear
Linear project management — issues, cycles, and projects via GraphQL API.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.