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 X-School-Academy/skill-pilot --skill dev-swarm-project-restoregit clone --depth 1 https://github.com/X-School-Academy/skill-pilotWrote 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/x-school-academy/skill-pilot/dev-swarm-project-restore)<a href="https://agentmods.dev/skills/x-school-academy/skill-pilot/dev-swarm-project-restore"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/dev-swarm-project-restore/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/x-school-academy/skill-pilot/dev-swarm-project-restore"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/dev-swarm-project-restore.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.00057 | $0.00540 |
| Opus 5.5 | $0.00023 | $0.00216 |
| Sonnet 5.5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
dev-swarm-project-restore 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 16d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Builder - Project Restore
This skill restores an existing project to the workspace root from an archive, remote git repo, or local codebase, including re-adding {SRC} and reconstructing missing docs when needed.
When to Use This Skill
- User asks to restore a project from
99-archive/ - User wants to restore a project from a remote git repository or a non-archived local codebase
- User needs
ideas.md, stage folders, or sprints reconstructed to resume work
Your Roles in This Skill
See dev-swarm/docs/general-dev-stage-rule.md for role selection guidance.
Role Communication
See dev-swarm/docs/general-dev-stage-rule.md for the required role announcement format.
Instructions
Follow these steps in order:
Step 1: Archive the Current Project
Archive the current project using agent skill dev-swarm-project-archive.
Step 2: Identify the Restore Source
Confirm whether the source is:
99-archive/{archive-folder}- Remote git repository URL
- Local codebase path (not created by archive; with or without git history)
Record the source in your notes before proceeding.
Step 3: Restore the Project
- If restoring from
99-archive/, followreferences/restore-procedure.md. - If restoring from a remote git repo or local codebase, follow
references/external-restore.md.
Step 4: Reverse-Engineer Missing Docs (If Needed)
If the codebase has little or no documentation, follow references/reverse-engineering.md to reconstruct:
ideas.md- stage folders
00-*through10-* - sprints and backlogs in
10-sprints/ - feature specs under
features/
Expected Output
- Archived project content restored to workspace root
ideas.mdpresent at the root{SRC}/re-added as a submodule at the correct commit99-archive/retains the archived snapshot- Reconstructed stages, sprints, and features when docs were missing
Key Principles
- Keep the restore process reversible and traceable in git history
- Prefer existing git history to restore the
{SRC}submodule state - Ask for user approval before destructive or irreversible operations
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.
- 16d ago First seen · 67 lines · 57 tokens per session scan A 0efc1251ab41
dev-swarm-project-restore is a skill published in the GitHub repository X-School-Academy/skill-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 540 once invoked, about $0.0002 per session on Opus 5.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-10-02.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…
implement-issue
Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.