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 GSA-TTS/mcp-hackathon-template --skill ibm-cloud-iaas-deploygit clone --depth 1 https://github.com/GSA-TTS/mcp-hackathon-templateWrote 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/gsa-tts/mcp-hackathon-template/ibm-cloud-iaas-deploy)<a href="https://agentmods.dev/skills/gsa-tts/mcp-hackathon-template/ibm-cloud-iaas-deploy"><img src="https://agentmods.dev/badge/skills/gsa-tts/mcp-hackathon-template/ibm-cloud-iaas-deploy/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/gsa-tts/mcp-hackathon-template/ibm-cloud-iaas-deploy"><img src="https://agentmods.dev/badge/skills/gsa-tts/mcp-hackathon-template/ibm-cloud-iaas-deploy.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.00112 | $0.01799 |
| Opus 5.5 | $0.00045 | $0.00720 |
| Sonnet 5.5 | $0.00022 | $0.00360 |
| Haiku 4.5 | $0.00011 | $0.00180 |
Grade C, and why
cr-code-engine-deploy scanned grade C with 2 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 2d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://clis.cloud.ibm.com/install/linux | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://cr-helper-api.2fm39a1i8ok7.ca-tor.codeengine.appdomain.cloud/get-script \ How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSA Hackathon — Container Registry & Code Engine Deploy
Walk the participant through every step: retrieving their personalised helper script, installing tooling, creating credentials, pushing their image, and deploying on Code Engine.
Step 1 — Identify the student
Ask the participant for their initials using ask_followup_question.
Ask the participant for their student number or cloud account name using ask_followup_question.
Accept either form:
"Student 7"/"7"/"student 7""itz-saas-813"
The Container Registry and Code Engine instances the participants have access to are shared tenants. To help distinguish this participant's assets from any others, make sure that container images, registry and API keys, deployed applications, and other assets have the participant's initials in the name, (e.g., "local-container-app-jmd" or "gsa-jmd-mcp-app" as example image names for Jane Marie Doe).
Step 2 — Retrieve the personalised helper script
Use execute_command to POST to the self-service API and save the script locally:
curl -X POST https://cr-helper-api.2fm39a1i8ok7.ca-tor.codeengine.appdomain.cloud/get-script \
-H "Content-Type: application/json" \
-d '{"student": "Student <N>"}' \
-o ~/push-to-cr.sh && chmod +x ~/push-to-cr.sh
After saving, display the contents so the participant can verify IMAGE_NAME, RESOURCE_GROUP,
and CR_NAMESPACE are correct for their account:
cat ~/push-to-cr.sh
Step 3 — Install ibmcloud CLI (if not present)
Check whether the CLI is already installed:
ibmcloud version
If the command is not found, install it:
curl -fsSL https://clis.cloud.ibm.com/install/linux | sh
Verify:
ibmcloud version
Step 4 — Install the Container Registry plugin (if not present)
Check:
ibmcloud cr version
If not found, install:
ibmcloud plugin install container-registry -r 'IBM Cloud'
Verify:
ibmcloud cr version
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.
- 2d ago First seen · 262 lines · 112 tokens per session scan C b8ff37c86ab6
cr-code-engine-deploy is a skill published in the GitHub repository GSA-TTS/mcp-hackathon-template (10 stars, last pushed 3d ago), licensed MIT. It adds 112 tokens to every session and 1,799 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-27.
Other skills, from other repositories
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, profile management, policy iteration, settings, service exposure, BYOC workflows, and attached-provider inference. Covers basic through advanced multi-step workflows. Trigger…
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
cdf-orchestration-setup
Use when the user asks to deploy, install, reinstall, redeploy, upgrade, or connect to the CDF Orchestration Airflow controller. Owns the end-to-end deploy sequence and runs the cdf-orchestration-preflight audit first. Covers make setup, controller image builds, Helm installation, controller connection…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.