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 dasein108/slope-studio --skill marketing-autopilotgit clone --depth 1 https://github.com/dasein108/slope-studioWrote 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/dasein108/slope-studio/marketing-autopilot)<a href="https://agentmods.dev/skills/dasein108/slope-studio/marketing-autopilot"><img src="https://agentmods.dev/badge/skills/dasein108/slope-studio/marketing-autopilot/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/dasein108/slope-studio/marketing-autopilot"><img src="https://agentmods.dev/badge/skills/dasein108/slope-studio/marketing-autopilot.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.00126 | $0.00873 |
| Opus 5 | $0.00063 | $0.00436 |
| Sonnet 5 | $0.00025 | $0.00175 |
| Haiku 4.5 | $0.00013 | $0.00087 |
Grade A, and why
marketing-autopilot 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 11d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
marketing-autopilot — run the loop on its own
The loop self-improves only if it keeps turning. This driver turns it. The hard part —
a published video must mature ~48–72h before its metrics mean anything — is handled by the
engine (studio/marketing/loop.py): it's a state machine over time, so each tick does the single
action that's actually due, never blindly publish→measure in one go.
One tick = ask the engine, do the one due action
studio marketing tick --channel <name> --json
Returns the next action with everything you need:
next |
what to do (agent-driven) |
|---|---|
measure |
studio marketing measure --channel <name> — measure_due videos have matured |
learn |
invoke marketing-measure-learn (its learn step: reflect → strategy); enough new measurements accrued |
ideate |
invoke marketing-ideate (web-search + recall → bets); backlog is low |
produce |
invoke marketing-deploy for produce_entry at produce_max_cost |
idle |
nothing due — sleep until the next tick (maturation / cadence wait) |
Do that ONE action, then tick again. Prefer the lego-block skills for the creative steps
(ideate/learn/produce) so the thinking is yours; measure is deterministic.
Running it continuously
Pick a cadence (ticks every few hours are plenty — the engine gates the real timing):
- Agent-driven (smartest): use the /loop skill to re-invoke this skill on an interval,
or /schedule to register a cron routine. Each firing:
tick --json→ do the due action. - Headless (no agent):
studio marketing autopilot --channel <name> [--produce]does one tick using the SCRIPTED ideate/learn fallbacks. Producing spends money + publishes, so it's gated behind--produce. Wire it to cron for fully unattended operation.
Before first run — configure the channel
studio marketing budget --channel <name> --per-minute 0.40 # or --per-video 0.60 (sizes --max-cost)
studio marketing tick --channel <name> # see what it would do
Cadence/maturation knobs live in Journal.loop (maturation_hours 60, min_hours_between_produces
20, daily_produce_cap 2, learn_every 3, backlog_min 2, target_duration_s 60) — edit
runs/_marketing/<name>/journal.json to tune.
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.
- 11d ago First seen · 65 lines · 126 tokens per session scan A 57177ae1ebbd
marketing-autopilot is a skill published in the GitHub repository dasein108/slope-studio (3 stars, last pushed 1mo ago), licensed MIT. It adds 126 tokens to every session and 873 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
dws
A command-line guide for DingTalk, a workplace platform with chat, documents, calendars, approvals, tasks, and other business tools.
package-author
A packaging guide for turning scripts, skills, or an MCP service into a standard plugin package. MCP is a way for an AI assistant to connect to external tools.
notes
Skill "notes" from Pinvou/pinvou-agent, covering ima notes, operations, write rules, examples and response handling.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.