Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/markmhendrickson/atelesnpx agentmods add skills/markmhendrickson/ateles/deploy-websiteWrote 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/markmhendrickson/ateles/deploy-website)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/deploy-website"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/deploy-website/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/markmhendrickson/ateles/deploy-website"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/deploy-website.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.00045 | $0.00603 |
| Opus 5.5 | $0.00018 | $0.00241 |
| Sonnet 5.5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
deploy-website 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 1mo 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.
What it actually says
Deploy Website
Scope: markmhendrickson website only. The website is a git submodule at execution/website/markmhendrickson/ and deploys from the markmhendrickson/markmhendrickson repo.
Required documents (load first)
docs/development_workflows_rules.mdc(Post markdown priority and deploy sync, Deployment verification, GitHub Actions re-run)execution/website/markmhendrickson/.github/workflows/deploy.yml
Workflow
1. Pre-deploy: sync → export → cache (from ateles repo root)
Run:
python3 execution/scripts/sync_posts_to_neotoma.py
execution/scripts/export_neotoma_website_data.sh
python3 execution/scripts/generate_website_cache.py
Outputs:
- Export (do not commit):
data/tmp/neotoma_website_export.json - Cache (commit; deploy artifact):
execution/website/markmhendrickson/react-app/cache/*.jsonexecution/website/markmhendrickson/react-app/cache/api/*.json
2. Update CI export secret (required)
GitHub Actions requires NEOTOMA_WEBSITE_EXPORT_JSON (in markmhendrickson/markmhendrickson) to be the base64-encoded contents of data/tmp/neotoma_website_export.json.
Update the secret whenever the export changes so CI can deterministically rebuild cache before deploy.
3. Deploy: commit + push the website repo (not ateles)
cd execution/website/markmhendrickson
# stage website changes (including react-app/cache and deploy.yml changes)
git status
git add -A
git commit -m "chore: deploy"
git push origin main
4. Verify deployment
- Use the verify-deployment workflow against
markmhendrickson/markmhendrickson. - Identify the deploy run and iterate fix → rerun until it succeeds.
Constraints
- Do not push
atelesto deploy the site; push theexecution/website/markmhendricksonsubmodule repo. - Do not commit the export JSON; commit only cache outputs.
posts.private.jsonis dev-only (production code paths do not load it).
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.
- 1mo ago First seen · 68 lines · 45 tokens per session scan A 373f9478a355
deploy-website is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 603 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-08-31.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
mcp-dependency-review
Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or other repo-scoped MCP config.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
workflow-automation
Workflow creation, execution, and template management. Automates complex multi-step processes with agent coordination. Use when: automating processes, creating reusable workflows, orchestrating multi-step tasks. Skip when: simple single-step tasks, ad-hoc operations.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.