coord-respawn-self SKILL.md skillA
coord-respawn-self from tekkiiiii/the-agency is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tekkiiiii/the-agency/coord-respawn-self@git:20260614.1eb2345Pins git:20260614.1eb2345 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tekkiiiii/the-agency
- Path
skills/coord-respawn-self/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260614.1eb2345, committed Jun 14, 2026
- First version recorded
- Jun 3, 2026
- Size
- 3,772 bytes
- Repository stars
- 6
- License
- none declared
Coord context-aware self-respawn. Invoked by a Coord agent when context window reaches 80% threshold mid-L3. Saves mid-L3 state, writes a continuation manifest, notifies the spawner (PD or Dept Head depending on caller role), and stops. The spawner then resumes the L3 with a fresh Coord. Enforces max 3 respawns per Coord per 24h. Use at clean task boundaries only — never mid-Executor-spawn or mid-ACK/NACK cycle.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /coord-respawn-self — Coord Context-Aware Self-Respawn
## When to Invoke
- **Mandatory:** when context window reaches 80% (CONTEXT_PCT_ALERT fires)
- **Proactive:** at a clean sub-task boundary within L3 when context > 70%
- **Never mid-Exec:** do not invoke while an Executor is awaiting APPROACH or CHECKPOINT
response — finish that exchange first, then respawn
## Respawn Counter Enforcement
Max 3 respawns per Coord per 24h. Uses the same counter mechanism as /respawn-self:
`~/.claude/state/respawn-counters/coord-{l3-name}-{pun}.txt`
```bash
COORD_ID="coord-{l3-name}-{pun}"
COUNTER_FILE="$HOME/.claude/state/respawn-counters/$COORD_ID.txt"
NOW=$(date +%s)
DAY=86400
mkdir -p "$HOME/.claude/state/respawn-counters"
if [ -f "$COUNTER_FILE" ]; then
COUNT=$(awk '{print $1}' "$COUNTER_FILE")
RESET_AT=$(awk '{print $2}' "$COUNTER_FILE")
AGE=$(( NOW - RESET_AT ))
if [ "$AGE" -ge "$DAY" ]; then
COUNT=0
RESET_AT=$NOW
fi
else
COUNT=0
RESET_AT=$NOW
fi
if [ "$COUNT" -ge 3 ]; then
echo "RESPAWN_BLOCKED: max 3 respawns reached for $COORD_ID in 24h."
exit 1
fi
NEW_COUNT=$(( COUNT + 1 ))
echo "$NEW_COUNT $RESET_AT" > "$COUNTER_FILE"
…Read the whole file at its exact version.
How to install
mdr add tekkiiiii/the-agency/coord-respawn-self@sha256:3b5a474ac7e17022The line at the top of this page pins the label git:20260614.1eb2345, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_gtgl53uhgsef4t7j)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 3, 2026 and Jun 14, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260614.1eb2345 latest | 2026-06-14 | 1eb2345 | 3,772 B | A | view · diff |
| git:20260603.7c485a0 | 2026-06-03 | 7c485a0 | 3,366 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3772 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tekkiiiii/the-agency · 6 stars · license none declared · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gtgl53uhgsef4t7j GET https://markdownregistry.com/api/v1/resolve?ref=tekkiiiii/the-agency/coord-respawn-self GET https://markdownregistry.com/api/v1/blob/3b5a474ac7e1702279e18fb4e0634302c91c3e6528434a5a16eaf548c329d077
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.