Borrowing it
Nothing to install: this file belongs to sussdorff/timing-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sussdorff/timing-cli/main/.agents/skills/intake/SKILL.mdgit clone --depth 1 https://github.com/sussdorff/timing-cliWrote 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/sussdorff/timing-cli/intake)<a href="https://agentmods.dev/skills/sussdorff/timing-cli/intake"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/intake/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/sussdorff/timing-cli/intake"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/intake.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.00027 | $0.01085 |
| Opus 5.5 | $0.00011 | $0.00434 |
| Sonnet 5.5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
intake 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 24d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intake
Turn source notes into factory-ready hosted issues. The original request is the authority source: creating a work order and implementing it are different requested outcomes. This active session remains the original author; do not delegate authoring. Never run issue review automatically; review is a separate explicitly requested action.
The helpers ship in scripts/ of the installed intake skill root, not the
marketplace source path. Resolve $INTAKE_ROOT local-first and fail closed if none
exists: <repo>/.agents/skills/intake, <repo>/.claude/skills/intake,
~/.agents/skills/intake, ~/.claude/skills/intake. Never search the filesystem.
Establish the request
Read the provided source and preserve it in local .intake scratch space. With no
source, ask for the missing input. Before extraction, read
history.md and run scripts/issue_history.py for the
target repository. Surface duplicate matches before creating another work order.
Classify the requested outcome by meaning:
- author-only: create, file or track work; stop with the created issue.
- author-and-execute: fix, build or deliver the requested change; continue after author-check and persistence.
- unclear: ask only the question that decides between those outcomes.
Approve the boundary
One coherent outcome is one issue; implementation steps are internal work, not
sub-issues. When there is exactly one candidate, a clear target and requested outcome,
no duplicate choice and no competing boundary or Human Decision Gate, record
approval_source: original_request. Do not ask for a routine confirmation.
Ask only when multiple plausible candidate boundaries remain, whether to append
to the existing issue or create a new one is unresolved, the target repository is
ambiguous, the requested outcome is unclear, or a product/architecture/policy choice
is needed. Record approval_source: explicit_hitl for that decision. Never repeat
approval already given for the same scope.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 24d ago Changed · +8 lines cd8a3c954a66
- 1mo ago Changed · +6 lines 4baba3ace230
- 1mo ago First seen · 74 lines · 27 tokens per session scan A 08da016df736
intake is a skill published in the GitHub repository sussdorff/timing-cli (1 stars, last pushed 10d ago), licensed MIT. It adds 27 tokens to every session and 1,085 once invoked, about $0.0001 per session on Opus 5.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-24.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.