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 Abilityai/cornelius --skill scheduled-rungit clone --depth 1 https://github.com/Abilityai/corneliusWrote 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/abilityai/cornelius/scheduled-run)<a href="https://agentmods.dev/skills/abilityai/cornelius/scheduled-run"><img src="https://agentmods.dev/badge/skills/abilityai/cornelius/scheduled-run.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.01397 |
| Opus 5 | $0.00008 | $0.00698 |
| Sonnet 5 | $0.00003 | $0.00279 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade A, and why
scheduled-run 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduled Run
Wrapper that runs any playbook with git sync. Use this for all scheduled executions to ensure:
- Latest changes pulled before running
- All changes committed and pushed after running
Purpose
Ensures scheduled playbooks on Trinity stay in sync with the GitHub repository.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Git repo | .git/ |
✓ | ✓ | Pull before, commit+push after |
| Playbook output | varies | ✓ | Whatever the playbook produces |
Arguments
$ARGUMENTS = The playbook name to run (e.g., refresh-index, coherence-sweep)
Process
Step 1: Pull Latest Changes
git pull --rebase
If conflicts, abort and log error. Do NOT run the playbook on a dirty tree.
Step 2: Run the Playbook
Scheduled playbooks run at the core read-scope by default. BRAIN_READ_SCOPE
is unset here, so every run_search.sh / run_connections.sh call inside the
playbook fails closed to core (the fingerprint) - which is the intended scope
for incubation-loop, refresh-index, coherence-sweep, gjopen-refresh, and
ai-crystallize. Perception/cross-domain playbooks that legitimately need non-core
content (e.g. domain-watch) set a wider BRAIN_READ_SCOPE=... inline on their
own search commands; do not widen it here. (Setting export BRAIN_READ_SCOPE=core
here would be a redundant fail-safe - the default is already core - and would not
propagate across the separate Bash invocations a playbook makes anyway.)
Invoke the specified playbook using the Skill tool:
Skill: $ARGUMENTS
Wait for completion.
Step 3: Check for Changes
git status --porcelain
If no changes, skip to completion.
Step 4: Commit Changes
git add -A && git commit -m "$(cat <<'EOF'
Scheduled: $ARGUMENTS $(date '+%Y-%m-%d %H:%M')
Automated execution via /scheduled-run
Co-Authored-By: Claude <[email protected]>
EOF
)"
Step 5: Push to Remote
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 · 133 lines · 16 tokens per session scan A 30a06ab4fd9e
scheduled-run is a skill published in the GitHub repository Abilityai/cornelius (106 stars, last pushed 14d ago), licensed MIT. It adds 16 tokens to every session and 1,397 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".