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 saajunaid/caddis-plugin --skill port-to-githubgit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/port-to-github)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/port-to-github"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/port-to-github/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/saajunaid/caddis-plugin/port-to-github"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/port-to-github.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.00118 | $0.04385 |
| Opus 5.5 | $0.00047 | $0.01754 |
| Sonnet 5.5 | $0.00024 | $0.00877 |
| Haiku 4.5 | $0.00012 | $0.00439 |
Grade A, and why
port-to-github 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 13d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
port-to-github
Move one app to GitHub without losing history, leaking a secret, or breaking its deploy.
The work is in six phases, plus the content policy (2b). Each ends in a check that can FAIL. Do not start a phase until
the one before it passed. Scripts are in scripts/ next to this file. They are PowerShell 7
(pwsh); the parts that run on a remote box are Windows PowerShell 5.1 compatible.
| Phase | Script | Changes anything outside this machine? |
|---|---|---|
| 1. Stage the source | Get-PortSource.ps1 |
No. The source is only read. |
| 2. Readiness | Test-PortReadiness.ps1 |
No. |
| 2b. Content policy | Test-PortContentPolicy.ps1, New-PortRuntimeManifest.ps1, Invoke-PortHistoryClean.ps1 |
No. Rewrites only the local stage. |
| 3. Publish | Publish-PortToGitHub.ps1 |
Yes: creates a GitHub repo and pushes. |
| 4. CI | Convert-PortWorkflow.ps1, Test-PortWorkflowParses.ps1 |
Yes: a feature branch and a PR. |
| 5. Cutover | Switch-CheckoutOrigin.ps1 |
Yes: changes where a deploy host pulls from. |
| 6. Retire the old host | manual, see references/old-host.md |
Yes, and can be destructive. |
Stop and ask the user before phases 3, 5 and 6. Each one is outward-facing. Say exactly what will be created or changed, on which host, and how to undo it.
Not every port needs every phase. A folder that never had CI or a deploy host ends after phase 3. Say which phases apply and why, before you start.
Before you start
- Read the project config, if one exists:
.caddis/port-to-github.jsonin the repo you are working from (or$env:PORT_TO_GITHUB_CONFIG). It sets the GitHubowner,visibility, staging folder, the name for the old remote, dependency hosts and their secrets, andprojectNotes- pointers to the project's own rules. Read every fileprojectNotesnames before phase 4. Project rules beat this skill. The shape is inreferences/config.example.json. gh auth statusmust show an account that can create repos in the owner.gitmust be able to push to github.com (rungh auth setup-gitonce if not).- Find the authoritative copy. If a folder is a clone of a server, port from the SERVER URL, not the folder: the folder may lack branches the server has. Port from a folder only when it is the only copy, or when it holds commits the server lacks. Phase 1 reports both cases.
What ships with it
14 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.
- references/ci-and-credentials.md 4.0 KB
- references/config.example.json 773 B
- references/old-host.md 3.4 KB
- scripts/Compare-PortRefs.ps1 2.7 KB runs code
- scripts/Convert-PortWorkflow.ps1 4.5 KB runs code
- scripts/Get-PortSource.ps1 27 KB runs code
- scripts/Invoke-PortHistoryClean.ps1 7.5 KB runs code
- scripts/New-PortRuntimeManifest.ps1 18 KB runs code
- scripts/PortCommon.ps1 5.2 KB runs code
- scripts/Publish-PortToGitHub.ps1 10 KB runs code
- scripts/Switch-CheckoutOrigin.ps1 9.8 KB runs code
- scripts/Test-PortContentPolicy.ps1 12 KB runs code
- scripts/Test-PortReadiness.ps1 13 KB runs code
- scripts/Test-PortWorkflowParses.ps1 2.7 KB runs code
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.
- 13d ago Changed · +5 lines · -23 tokens per session c8cde20c561e
- 19d ago Changed · -90 tokens per session d9f80a9246ed
- 27d ago Changed · +61 lines · +64 tokens per session 4b8ff6cc1c0f
- 29d ago First seen · 232 lines · 167 tokens per session scan A 036f93acc4af
port-to-github is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 118 tokens to every session and 4,385 once invoked, about $0.0005 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-09-19.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.