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 markmhendrickson/ateles --skill create-websitegit clone --depth 1 https://github.com/markmhendrickson/atelesWrote 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/create-website)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/create-website"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/create-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/create-website"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/create-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.00046 | $0.00511 |
| Opus 5.5 | $0.00018 | $0.00204 |
| Sonnet 5.5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
create-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
Create Website
Create a new website in its own repository and add it as a submodule under execution/website/[name]/. Never create website files directly in the parent repository.
When to Use
Use this skill when:
- User says "create new website", "add website for [domain/name]"
- User wants a new site (e.g. for a new domain) as a separate repo and submodule
Required Documents (load first)
- Website development: docs/development_workflows_rules.mdc (Website Development)
Workflow
- Create new private GitHub repository for the website. Use a simple domain-based name (e.g.
dionysiandesignsfor dionysiandesigns.com). - Initialize repository with website files: HTML, CSS, assets, README.md with deployment instructions and contact information.
- Add as submodule in
execution/website/[name]/directory (e.g.execution/website/dionysiandesigns/). - Commit and push website changes within the submodule repository.
- Update parent repository if the submodule reference changed (commit submodule pointer in ateles).
Constraints
- Always create websites as their own repositories; add as submodule in
execution/website/[name]/. - Never create website files directly in the parent repo or in a root
websites/directory. - Location:
execution/website/— websites are execution artifacts per three-layer architecture. - Submodule structure: website files in submodule root; README.md with deployment instructions; parent tracks submodule at
execution/website/[name]/.
Related Rules
- docs/development_workflows_rules.mdc — Website Development
- Examples:
execution/website/dionysiandesigns/,execution/website/hendricksonserrano/
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 · 45 lines · 46 tokens per session scan A d056fe6db866
create-website is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 511 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
local-llm-tool
A local LLM execution tool. Requests text generation and chat from models on GPU via Ollama or vLLM. Use when: Use when: on-premise inference, calling Ollama endpoints, or needing summaries and generation with local models.
understand-codebase
Understand an unfamiliar codebase or plan a change safely, using Spine's deterministic knowledge-graph MCP tools. Reach for this before answering structural questions about a repo you don't know, before editing code, or when debugging — it hands you engineering decisions (what a change breaks, what's untested, where a…
continue
Autonomous work — find and execute ready tasks.
review-pr
A pull-request review skill for evaluating proposed code changes and posting a quality verdict. A pull request is a request to merge changes into a shared codebase.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
roadmap
An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.