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/flyteorg/flyte-agent-plugins/flyte-sdk-authornpx skills add flyteorg/flyte-agent-plugins --skill flyte-sdk-authorgit clone --depth 1 https://github.com/flyteorg/flyte-agent-pluginsWrote 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/flyteorg/flyte-agent-plugins/flyte-sdk-author)<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-sdk-author"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-sdk-author.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.00123 | $0.03175 |
| Opus 5 | $0.00062 | $0.01588 |
| Sonnet 5 | $0.00025 | $0.00635 |
| Haiku 4.5 | $0.00012 | $0.00317 |
Grade A, and why
flyte-sdk-author 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 3d 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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flyte 2 SDK Author Skill
Create Flyte 2 workflows, tasks, and apps from scratch using pure Python — no DSL.
Grounding References
| Resource | URL |
|---|---|
| Official docs | https://www.union.ai/docs/v2/flyte |
| Docs index (LLMs) | https://www.union.ai/docs/v2/flyte/llms.txt |
| SDK API reference | https://www.union.ai/docs/v2/union/api-reference/flyte-sdk/ |
| CLI API reference | https://www.union.ai/docs/v2/union/api-reference/flyte-cli/ |
| flyte-sdk source | https://github.com/flyteorg/flyte-sdk |
| Example code | https://github.com/unionai/unionai-examples |
| Flyte MCP tools | Available via the flyte-cluster and flyte-docs MCP servers |
Ground unfamiliar APIs in real examples. When unsure of a current Flyte 2 API, or for a pattern not shown below, and the flyte-docs search tools are available, search them first — by exact symbol (TaskEnvironment, flyte.io.File, map_task), since matching is literal substring, not semantic — then adapt a real example rather than inventing one, and cite the file or section you pulled it from. (Flyte 2 is not flytekit; priors are often wrong.)
Tool Priority
- Flyte MCP — if the harness has Flyte MCP tools, prefer them for inspecting and discovering registered tasks, listing and interacting with runs, executing a task remotely, managing apps and triggers, and searching Flyte SDK examples and docs.
flyteCLI — for local commands:flyte run,flyte deploy,flyte serve,flyte create config,flyte start devbox- Python SDK — for anything the CLI/MCP can't do (custom task environments, type transformers, dynamic workflows, programmatic run control)
Core Patterns
TaskEnvironment + @env.task (recommended)
import flyte
import flyte.io
env = flyte.TaskEnvironment(
name="training",
image=flyte.Image.from_debian_base(python_version=(3, 12)).with_pip_packages(
"pandas", "torch", "transformers",
),
)
@env.task(retries=2, cache="auto")
async def preprocess(data: list[str]) -> flyte.io.File:
# ETL: clean + write to remote storage
...
return flyte.io.File(path="/tmp/output.parquet")
@env.task
async def train(data_path: flyte.io.File) -> flyte.io.File:
# ML: model training
...
return flyte.io.File(path="/tmp/model.pt")
@env.task
async def evaluate(model_path: flyte.io.File) -> dict:
# ML: evaluation
return {"accuracy": 0.95, "f1": 0.92}
@env.task
async def main(data: list[str]) -> dict:
path = await preprocess(data)
model = await train(path)
return await evaluate(model)
if __name__ == "__main__":
import asyncio
result = asyncio.run(main(["a", "b", "c"]))
print(result)
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.
- 3d ago First seen · 414 lines · 123 tokens per session scan A ee41d603bd01
flyte-sdk-author is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 123 tokens to every session and 3,175 once invoked, about $0.0006 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
bump-dependency
Bumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
pause
Pause Mem0 memory capture on this machine. Use when the user wants to stop memories being recorded, for example for private work or experiments.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.