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 Obedience-Corp/festival --skill cross-campaigngit clone --depth 1 https://github.com/Obedience-Corp/festivalWrote 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/obedience-corp/festival/cross-campaign)<a href="https://agentmods.dev/skills/obedience-corp/festival/cross-campaign"><img src="https://agentmods.dev/badge/skills/obedience-corp/festival/cross-campaign/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/obedience-corp/festival/cross-campaign"><img src="https://agentmods.dev/badge/skills/obedience-corp/festival/cross-campaign.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.00603 |
| Opus 5 | $0.00026 | $0.00302 |
| Sonnet 5 | $0.00010 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
cross-campaign 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 6d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Camp Operations
A camp was previously called a campaign; treat the two words as the same thing whenever the user says either one.
When the user references another camp or a project that isn't in the current camp, use these commands to locate and access it.
Discovery
camp list # Show all registered camps with paths
camp list --format json # JSON output for scripting
camp list --format simple # Names only
Navigation
camp switch <name> # Switch to a camp (interactive if no name)
camp switch <name> --print # Print path only (for cd or scripting)
cd "$(camp switch --print <name>)" # Navigate without shell init
Reading From Another Camp
Use the path from camp list to read files directly:
# Get the path
camp list --format json | jq -r '.[] | select(.name=="My_Tools") | .path'
# Or just read camp list output and use the path
cat "$(camp switch --print My_Tools)/projects/samantha/main.go"
Transferring Files Between Camps
camp transfer other-camp:docs/design.md docs/ # Pull file here
camp transfer docs/plan.md other-camp:docs/plan.md # Push file there
camp transfer other:festivals/F001/ festivals/reference/ # Pull directory
Syntax: camp-name:relative/path. Paths without a prefix resolve to the
current camp.
Common User Phrases That Trigger This Skill
- "In the X camp, there's a project called..." (or "in the X campaign...")
- "We implemented this in another camp..."
- "Check how Y was done in Z camp"
- "Pull/copy that file from the other camp"
- "Find which camp has project X"
Workflow
- Run
camp listto find the target camp - Use the path to read/explore the referenced code
- If the user wants to copy something, use
camp transfer - If you need extended work in the other camp, use
camp switch
Common Mistakes
- Asking the user for the camp path instead of running
camp list - Forgetting that
camp transfercopies, never moves - Using
camp switchwhen you only need to read a file (just use the path fromcamp list) - Not checking
camp listwhen the user says "the other camp" (or "campaign") or references a project you can't find locally
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.
- 6d ago Changed · +5 lines · +2 tokens per session 7b1a2232f79d
- 10d ago First seen · 69 lines · 50 tokens per session scan A 564dab112a58
cross-campaign is a skill published in the GitHub repository Obedience-Corp/festival (49 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 603 once invoked, about $0.0003 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-30.
Other skills, from other repositories
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
workspace-prune-working
Clean up .aiwg/working/ by promoting, archiving, or deleting temporary files.
workspace-realign
Reorganize and update .aiwg/ documentation to reflect current project reality.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
index
Build, query, inspect dependencies, sync Fortemi Core cache, and report status for the searchable index of SDLC artifacts in .aiwg/.
migrate-hook
Migrate existing CLAUDE.md full-injection to the AIWG.md hook file architecture.