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 agentmods add skills/markmhendrickson/ateles/deploy-websitenpx skills add markmhendrickson/ateles --skill deploy-websitegit clone --depth 1 https://github.com/markmhendrickson/atelesWhat 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 | $0.00045 | $0.00603 |
| Opus 5 | $0.00023 | $0.00302 |
| Sonnet 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 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.
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.
- 2d 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 4d ago), licensed MIT. It adds 45 tokens to every session and 603 once invoked, about $0.0002 per session on Opus 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
10x-orchestrator
MANDATORY - The core brain of 10X Vibe Marketer. You are the autonomous CMO orchestrating a full marketing agency of 12 specialist departments. Load this skill for ANY marketing task - content creation, SEO, campaigns, strategy, research, analytics, outreach, social media, email, paid ads, branding, funnel…
10x-setup
First-time setup and initialization for 10X Vibe Marketer. Includes an interactive wizard that lets users choose their database, features, marketing focus, visual tools, and tracking preferences. Checks setup.log to determine if setup has already been completed. Run via /setup or auto-triggered on first use.
10x-visualizer
Generate visual marketing deliverables — strategy boards, funnel diagrams, flowcharts, journey maps, dashboards, and more — using TLDraw SDK (local .tldr files). Each department agent creates visuals for their own domain. Invoke with /report.
community-manager
Skill "community-manager" from OpenAnalystInc/Vibe-Marketer, covering community manager — 10x vibe marketer, identity, step-by-step execution, cli visual identity and expertise.
10x-research
The research orchestration engine for 10X Vibe Marketer. Powers multi-platform, real-time research across 13 platforms using Claude in Chrome and WebSearch/WebFetch. Spawns platform-specific research agents in parallel, consolidates findings through the research lead, and delivers actionable marketing intelligence.
affiliate-specialist
Skill "affiliate-specialist" from OpenAnalystInc/Vibe-Marketer, covering affiliate specialist — 10x vibe marketer, identity, step-by-step execution, cli visual identity and expertise.