Borrowing it
Nothing to install: this file belongs to salazarsebas/Cougr. 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/salazarsebas/Cougr/main/.claude/skills/deploy-stellar-mainnet/SKILL.mdgit clone --depth 1 https://github.com/salazarsebas/CougrWrote 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/salazarsebas/cougr/deploy-stellar-mainnet)<a href="https://agentmods.dev/skills/salazarsebas/cougr/deploy-stellar-mainnet"><img src="https://agentmods.dev/badge/skills/salazarsebas/cougr/deploy-stellar-mainnet/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/salazarsebas/cougr/deploy-stellar-mainnet"><img src="https://agentmods.dev/badge/skills/salazarsebas/cougr/deploy-stellar-mainnet.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.00092 | $0.01291 |
| Opus 5.5 | $0.00037 | $0.00516 |
| Sonnet 5.5 | $0.00018 | $0.00258 |
| Haiku 4.5 | $0.00009 | $0.00129 |
Grade A, and why
deploy-stellar-mainnet 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 today.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this skill does
Walk through three gates. Do not let the user skip a gate.
Gate 1: Pre-deployment verification
Check each item. If any fails, stop and fix before moving on.
Contract correctness:
- All contract tests pass on testnet (
stellar contract invoke ...against a deployed testnet copy) - At least one end-to-end integration test exists (deploy → invoke → assert state)
- Storage usage profiled - no unbounded growth, TTL extension wired up for long-lived data
- Authorization paths reviewed - every
require_authis justified, no missing auth on sensitive operations - CPI (cross-contract call) safety considered if calling other contracts (reentrancy patterns)
Security:
- No
unwrap()on user-controlled paths - use?with proper error types - No panics on malformed input
- Integer overflow handled -
checked_*arithmetic ori128where appropriate - Admin operations gated by explicit role checks
- If accepting assets, contract uses the Stellar Asset Contract (SAC) correctly
Audit / formal verification (for high-value contracts):
- At least informal peer review by someone outside the team
- For contracts holding >$100K TVL or critical infra: third-party audit (Certora, OtterSec, Code4rena are active on Stellar - see
data/lumenloop/audits/registry.json) - If skipping audit, document explicit risk acceptance with reasoning
Operational:
- Admin keys: who holds them, where stored (hardware wallet preferred, NOT in CI secrets)
- Upgrade path: contract is upgradeable via WASM hot-swap, OR explicitly immutable and documented as such
- Emergency pause exists and is admin-only if user-facing funds are involved
- Deploy SOPs documented (1-pager - at minimum: who can deploy, network config, contract ID location)
Gate 2: Deployment mechanics
Check stellar CLI is installed: stellar --version (install: cargo install stellar-cli or brew install stellar-cli).
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.
- today First seen · 109 lines · 92 tokens per session scan A 5319abf99e06
deploy-stellar-mainnet is a skill published in the GitHub repository salazarsebas/Cougr (53 stars, last pushed 17d ago), licensed MIT. It adds 92 tokens to every session and 1,291 once invoked, about $0.0004 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-11-07.
deploy-stellar-mainnet compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| deploy-stellar-mainnetsalazarsebas/Cougr | Skill | 53 | 17d ago | MIT | A | 92 | Claude Code |
| frontend-designrylsherdamz-rgb/stellar-forge | Skill | 17 | 5d ago | MIT | A | 51 | Claude Code |
| stellar-forgerylsherdamz-rgb/stellar-forge | Skill | 17 | 5d ago | MIT | A | 82 | Claude Code |
| smart-contractsrylsherdamz-rgb/stellar-forge | Skill | 17 | 5d ago | MIT | A | 44 | Claude Code |
| dapprylsherdamz-rgb/stellar-forge | Skill | 17 | 5d ago | MIT | A | 48 | Claude Code |
| stellar-mcprylsherdamz-rgb/stellar-forge | Skill | 17 | 5d ago | MIT | A | 61 | Claude Code |
| datarylsherdamz-rgb/stellar-forge | Skill | 17 | 5d ago | MIT | A | 41 | Claude Code |