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 helleOPP/anycross-skill-creator --skill anycross-creatorgit clone --depth 1 https://github.com/helleOPP/anycross-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/helleopp/anycross-skill-creator/anycross-creator)<a href="https://agentmods.dev/skills/helleopp/anycross-skill-creator/anycross-creator"><img src="https://agentmods.dev/badge/skills/helleopp/anycross-skill-creator/anycross-creator/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/helleopp/anycross-skill-creator/anycross-creator"><img src="https://agentmods.dev/badge/skills/helleopp/anycross-skill-creator/anycross-creator.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.00243 | $0.02546 |
| Opus 5 | $0.00121 | $0.01273 |
| Sonnet 5 | $0.00049 | $0.00509 |
| Haiku 4.5 | $0.00024 | $0.00255 |
Grade A, and why
anycross-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 10d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AnyCross Creator
Build AnyCross workflows as flow.json inside a .zip, generated by a Python script so the output is reproducible and reviewable.
The hard part of AnyCross is not the logic — it is that every connector ID, operation ID, credential ID, and parameter shape is tenant- and version-specific. Two Bitable connectors exist in the wild (7241926900765982725 v2.0 and 7576576101812538807 v2.7) with different operation IDs and different parameter names for the same action. Guessing these produces a zip that imports but silently fails, or fails to import at all. So the workflow below is built around one rule: copy IDs from a real export, never from memory.
Step 0 — Ask for a template before building anything
Before writing a single line of generator code, ask the user:
Do you have an AnyCross workflow that already runs in this tenant? Export it to .zip and give me the path — I'll take the real connectorId / operationId / credentials / parameter shapes from it instead of guessing.
If you don't have one: which tenant is this, and is there any other workflow on the same tenant I could look at?
This question is not a formality — it is the single highest-leverage step. A template export gives, for free: the exact connector versions this tenant has installed, working credential IDs, the parameter names for each operation, and the spel paths that actually resolve.
Run the inspector on any template the user provides:
python <skill-dir>/scripts/inspect_export.py "<path-to.zip>"
python <skill-dir>/scripts/inspect_export.py "<path-to.zip>" --spel # also list every reference
It prints the node inventory (connector name/version/IDs), parameter keys per node, credential IDs, and spel references. Copy from that output.
If no template exists, say so plainly and fall back to references/connectors.md — but tell the user those IDs came from other tenants' exports and may not match theirs, so the first import is a probe, not a delivery. Then Step 4's error loop matters even more.
What ships with it
9 files 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.
- assets/generator_skeleton.py 8.0 KB runs code
- references/connectors.md 7.9 KB
- references/flow-schema.md 8.4 KB
- references/integrations.md 6.8 KB
- references/known-errors.md 8.2 KB
- references/larkbase.md 6.6 KB
- scripts/inspect_export.py 3.8 KB runs code
- scripts/pack_flow.py 1.4 KB runs code
- scripts/validate_flow.py 8.0 KB runs code
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.
- 10d ago First seen · 132 lines · 243 tokens per session scan A 5c80c3cf10c0
anycross-creator is a skill published in the GitHub repository helleOPP/anycross-skill-creator (2 stars, last pushed 1mo ago), licensed MIT. It adds 243 tokens to every session and 2,546 once invoked, about $0.0012 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
one-on-one-scheduler
A workflow for arranging, preparing, and reviewing one-to-one meetings between a mentor and a student. It coordinates times, gathers agenda information, and writes back meeting notes.
supervise-student
A study-accountability workflow that checks in with a student at set intervals and responds when they ask to be supervised. It supports online supervision through Feishu and an offline mode using Feishu with Temi’s visual system.
lark-cli
A command-line tool for working with Lark, also called Feishu, a workplace collaboration platform. It covers services such as calendars, meetings, documents, spreadsheets, messaging, tasks, approvals, and shared files.
lark-drive
A Feishu cloud-drive tool for managing online files and folders. Feishu cloud drive is a shared online storage area, similar to Google Drive or Dropbox.
lark-im
A skill for Feishu instant messaging, including one-to-one chats, group chats, threads, files, reactions, and interactive cards. Feishu is a workplace chat and collaboration platform.
lark-vc-agent
A tool for reading events from meetings that are happening now in Feishu, such as people joining, speaking, chatting, or sharing their screen. It can also send text messages or reactions into an ongoing meeting.