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/tile-ai/tilelang-ascend/tilelang-submodule-pullnpx skills add tile-ai/tilelang-ascend --skill tilelang-submodule-pullgit clone --depth 1 https://github.com/tile-ai/tilelang-ascendWrote 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/tile-ai/tilelang-ascend/tilelang-submodule-pull)<a href="https://agentmods.dev/skills/tile-ai/tilelang-ascend/tilelang-submodule-pull"><img src="https://agentmods.dev/badge/skills/tile-ai/tilelang-ascend/tilelang-submodule-pull.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 | $0.00103 | $0.01645 |
| Opus 5 | $0.00051 | $0.00822 |
| Sonnet 5 | $0.00021 | $0.00329 |
| Haiku 4.5 | $0.00010 | $0.00164 |
Grade A, and why
tilelang-submodule-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 4d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tilelang Third-Party Repository Auto-Pull
Overview
This skill provides automatic pulling of tilelang repository and its third-party code:
- Scheduled Pull: Executes pull every hour
- Error Handling: Automatically detects network errors, access failures, etc.
- Multiple Methods: Supports two pull methods with automatic switching
- Real-time Output: Pull process printed to terminal and log file in real-time
- Timeout Protection: Automatically stops after 10 hours of background running to prevent forgetting to close
Script Paths
All paths are relative to the current project root directory:
Assuming the current project is at /mnt/workspace/tilelang-ascend, then:
| File | Path | Description |
|---|---|---|
| Pull Script | .agents/skills/tilelang-custom-skill/tilelang-submodule-pull/scripts/auto_pull.sh |
Main script |
| Log File | .agents/skills/tilelang-custom-skill/tilelang-submodule-pull/logs/git_pull.log |
Pull log |
The script automatically detects the project root directory, no manual configuration needed.
Usage
1. Direct Run (Foreground)
bash .agents/skills/tilelang-custom-skill/tilelang-submodule-pull/scripts/auto_pull.sh
2. Background Run
nohup .agents/skills/tilelang-custom-skill/tilelang-submodule-pull/scripts/auto_pull.sh &
3. View Logs
tail -f .agents/skills/tilelang-custom-skill/tilelang-submodule-pull/logs/git_pull.log
Workflow
1. Configure git mirror source (using ghfast.top for acceleration)
2. Check if running time exceeds 10 hours (background run only)
↓ Exceeds 10 hours
3. Automatically stop script and log
↓ Not exceeded
4. Execute two commands simultaneously:
- git submodule update --init --recursive
- git pull --recurse-submodules
↓ If either fails
5. Wait 1 hour then retry the entire process
↓ Both succeed
6. Stop script
Error Detection
The script automatically detects the following errors:
Could not access: Cannot access submoduleerror: General errorfatal: Fatal errorFailed to clone: Clone failedunable to access: Cannot access URL
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.
- 4d ago First seen · 173 lines · 103 tokens per session scan A 97779f7e94e0
tilelang-submodule-pull is a skill published in the GitHub repository tile-ai/tilelang-ascend (358 stars, last pushed 7d ago), licensed MIT. It adds 103 tokens to every session and 1,645 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…