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 pullgit 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/pull)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/pull"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/pull/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/pull"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/pull.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.00013 | $0.02423 |
| Opus 5.5 | $0.00005 | $0.00969 |
| Sonnet 5.5 | $0.00003 | $0.00485 |
| Haiku 4.5 | $0.00001 | $0.00242 |
Grade A, and why
pull 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.
This is a copy
94% identical to pull — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pull
Pull latest commits from origin, committing local changes first, merging conflicts, and running setup scripts.
SUBMODULE MODE: If a submodule name is provided (e.g., /pull foundation), scope operations to that submodule only, not the main repository.
Configuration is read from foundation-config.yaml.
If submodule name provided:
- Check if submodule exists:
git submodule status <submodule-name> - Change to submodule directory:
cd <submodule-name> - Run pull workflow in submodule context
- Exit after submodule pull (do NOT pull main repository)
If no submodule name provided, proceed with main repository pull workflow below.
Workflow Overview
- Commit local changes using foundation commit command (if any uncommitted changes)
- Fetch latest from origin
- Pull latest commits (merge or rebase based on configuration)
- Resolve merge conflicts if they occur
- Run setup scripts as needed
Tasks
Step 1: Determine Scope
If submodule name provided:
-
Verify submodule exists:
if ! git submodule status <submodule-name> >/dev/null 2>&1; then echo "❌ Submodule not found: <submodule-name>" exit 1 fi -
Save parent directory and change to submodule directory:
ORIGINAL_DIR=$(pwd) # Save parent directory before cd cd <submodule-name> || exit 1 -
Update scope context (all subsequent operations in submodule)
If no submodule name provided, proceed with main repository context.
Step 2: Check for Uncommitted Changes
# Check if there are uncommitted changes
if git status --porcelain | grep -q .; then
echo "📝 Found uncommitted changes, committing first..."
# Use foundation commit command to commit changes
# Agent should invoke the commit command workflow:
# - Run security audit
# - Stage changes
# - Generate commit message
# - Commit changes
# - Push to origin if configured
# For agent: Use the foundation commit command workflow
# Invoke: `/commit <submodule-name>` (if submodule) or `/commit` (if main repo)
echo "✅ Local changes committed"
else
echo "✅ No uncommitted changes"
fi
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 · 317 lines · 13 tokens per session scan A fafd96d04da0
pull is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 2,423 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to pull, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
development-identity
Use the shared Paloma development identity for GitHub, signed commits and fleet SSH access in sandboxed.sh and Orb missions.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
git-commit
Stage, write, and structure git commits and pull requests cleanly. Read this before committing — for conventional-commit message format, when to split commits, and how to open a PR with the gh CLI.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.