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 oyi77/1ai-skills --skill content-publishergit clone --depth 1 https://github.com/oyi77/1ai-skillsWrote 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/oyi77/1ai-skills/content-publisher)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/content-publisher"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/content-publisher/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/oyi77/1ai-skills/content-publisher"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/content-publisher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 84 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 87 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 87 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00029 | $0.01204 |
| Opus 5 | $0.00015 | $0.00602 |
| Sonnet 5 | $0.00006 | $0.00241 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
content-publisher scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
user = requests.get("https://api.medium.com/v1/me", headers=headers).json()["data"]["id"] How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Publisher
When to Use
Trigger phrases:
- "content publisher"
- "Help me with content publisher"
Use cases:
- When the task matches this skill's domain expertise
When NOT to use:
- For tasks outside this skill's scope
Automates drafting and publishing articles to Substack and Medium with workflow automation.
When NOT to Use
- For one-off tasks that will never repeat
- When the process requires human judgment at every step
- When the cost of automation exceeds the cost of manual execution
Overview
Content Publisher automates workflow automation to reduce manual effort and increase reliability.
Workflow
# Example: Workflow automation
import schedule
import time
def run_workflow():
data = fetch_data()
processed = transform(data)
deliver(processed)
schedule.every().hour.do(run_workflow)
while True:
schedule.run_pending()
time.sleep(60)
- Define triggers — Set up events or schedules that initiate the automation
- Configure inputs — Specify data sources and parameters
- Design pipeline — Define the sequence of automated steps
- Add error handling — Set up retries, alerts, and fallback paths
- Test end-to-end — Validate the full automation with realistic data
- Deploy and monitor — Activate and track performance
Code Examples
Python: Medium Draft
import os, requests
def publish_medium(title, body, tags):
token = os.environ["MEDIUM_TOKEN"]
headers = {"Authorization": f"Bearer {token}", "Content-Type": "application/json"}
user = requests.get("https://api.medium.com/v1/me", headers=headers).json()["data"]["id"]
payload = {"title": title, "contentFormat": "markdown", "content": body,
"tags": tags[:5], "publishStatus": "draft"}
resp = requests.post(f"https://api.medium.com/v1/users/{user}/posts", headers=headers, json=payload)
resp.raise_for_status()
return resp.json()["data"]["url"]
Node.js: WordPress Post
export async function publishWP(title, content, tags) {
const auth = Buffer.from(`${process.env.WP_USER}:${process.env.WP_APP_PASSWORD}`).toString("base64");
const resp = await fetch(`${process.env.WP_URL}/wp-json/wp/v2/posts`, {
method: "POST", headers: { Authorization: `Basic ${auth}`, "Content-Type": "application/json" },
body: JSON.stringify({ title, content, status: "draft", tags }),
});
if (!resp.ok) throw new Error(`WP ${resp.status}`);
return (await resp.json()).link;
}
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.
- 12d ago First seen · 156 lines · 29 tokens per session scan A 64649da0901c
content-publisher is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,204 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-creator
Create custom AI subagents with proper plugin structure, persona generation, and companion routing skills.
anti-sleep
Keep a Mac awake with caffeinate during long builds, downloads, or supervised automation runs.
workflow-automation
Automate complex workflows and repetitive tasks using AI agents and tool integration. Use when user wants to create automated pipelines, integrate multiple services, or build task-specific agents.
hourly-rate-time
A time-management method based on assigning a high personal value to each hour. It treats time as a limited resource and uses that value to decide which tasks to do, outsource, or skip.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.