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/XAIHT/Tlamatininpx agentmods add skills/xaiht/tlamatini/skill_creatorWrote 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/xaiht/tlamatini/skill_creator)<a href="https://agentmods.dev/skills/xaiht/tlamatini/skill_creator"><img src="https://agentmods.dev/badge/skills/xaiht/tlamatini/skill_creator.svg" alt="Measured on agentmods" 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.00023 | $0.01039 |
| Opus 5 | $0.00012 | $0.00519 |
| Sonnet 5 | $0.00005 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
skill-creator 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Use this skill to bootstrap a new skill correctly the first time.
Procedure
-
Validate the inputs:
skill_namemust be kebab-case, all lowercase, ASCII letters/numbers/dashes only.runtimemust bein-processoracpx. Ifacpx,acpx_agentis required.
-
Create the directory
Tlamatini/agent/skills_pkg/${input.skill_name}/. -
Author
SKILL.mdwith this minimal scaffold:
---
name: ${input.skill_name}
description: ${input.description}
metadata:
tlamatini:
runtime: ${input.runtime}
acpx_agent: ${input.acpx_agent} # only if runtime=acpx
requires_tools: []
requires_mcps: []
budget:
max_iterations: 8
max_seconds: 120
max_tokens: 16000
permissions:
filesystem: { read: [], write: [] }
shell: []
network: deny
db: deny
inputs: []
outputs: []
triggers:
keywords: []
file_globs: []
---
# ${input.skill_name}
Describe the skill. Be concise. Body must stay under 8 KiB.
-
Run the linter:
python Tlamatini/agent/skills_pkg/_meta/lint.py -
Return
{ "skill_dir": "<path>", "lint_status": "<linter stdout last line>" }.
Constraints
- Do NOT write outside
Tlamatini/agent/skills_pkg/<skill_name>/. - Do NOT add a skill whose name collides with an existing one — the registry rejects duplicates. The lint step catches this.
- Body length cap is 8 KiB. Long playbooks belong in
references/<file>.mdinside the skill directory and should be referenced from the body, not inlined. - Skills with
runtime: acpxMUST setacpx_agentto a registered agent_id (seelist_acp_agents). - Scratch/output under
<app>/Temp(2026-06-02 policy): if the skill writes any temporary or intermediate file, target<app>/Temp— read theTLAMATINI_TEMPenv var, or (in-process) resolve viaagent/path_guard.py::resolve_temp_path— neverC:\Temp/%TEMP%, and declare that path inpermissions.filesystem.write. Files the user keeps (deliverables) go to their chosen path; only throwaway artefacts go to Temp. Seeprompt.pmtRule 15.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 114 lines · 23 tokens per session scan A 9be01120b6d0
skill-creator is a skill published in the GitHub repository XAIHT/Tlamatini (16 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,039 once invoked, about $0.0001 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-30.
Other skills, from other repositories
commit
Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.
review
Review current code changes for bugs, regressions, test gaps, and project-guideline violations.
tura
Work in the Tura agent-runtime repository. Use for Tura architecture, Rust backend, GUI/TUI, prompts, commands, providers, sessions, documentation, tests, packaging, and release work in this directory.
grade-and-fix-daedalus
How to grade a Daedalus run (or pasted agent transcript), root-cause the failure, and ship the fix to Daedalus CORE as a stacked PR — without modifying the prompt-vault sandbox (read-only grading). Covers recurring bug archetypes (Unicode punctuation patch mismatch, syntax-vs-type mislabel, emoji box misalignment…
add-slash-command
How to add a new slash command to Daedalus (src/commands), including the docs-sync step that breaks CI if skipped.
fix-typescript-build
How to fix a failing tsc/npm run build (type-check) run in a project, batching fixes into sprints to preserve context.