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/abilities --skill project-intakegit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilities/project-intake)<a href="https://agentmods.dev/skills/abilityai/abilities/project-intake"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/project-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/abilityai/abilities/project-intake"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/project-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.00110 | $0.04754 |
| Opus 5.5 | $0.00044 | $0.01902 |
| Sonnet 5.5 | $0.00022 | $0.00951 |
| Haiku 4.5 | $0.00011 | $0.00475 |
Grade A, and why
project-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 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Intake
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — e.g.
project-intake v1.6.1 — recent: arguments no longer break the config resolver. Then proceed.
Purpose
Route any actionable item from any source into the managed registry. This skill is headless — it never calls AskUserQuestion. It is called by domain skills, meeting-summary flows, crons, and composed pipelines. Output: the created or duplicate issue number.
This skill is the only sanctioned programmatic path for creating task issues. /project-task is for interactive human creation; /project-intake is for automated and composed creation.
Arguments
| Argument | Required | Description |
|---|---|---|
--project=<slug> |
yes | Target project slug (from project:<slug> label, or an internal project's folder name) |
--title="..." |
yes | Plain imperative title for the actionable item |
--source="..." |
yes | URL or short description of origin (meeting link, email subject, Slack permalink, ticket URL) |
--owner=<actor> |
no | Accountable party. Defaults to the project's primary owner from the epic. |
--priority=pN |
no | p1/p2/p3. Inherits from epic if omitted. |
--agent=<name> |
no | Executing agent label if immediately assignable. |
--waiting-on=<actor> |
no | The item is parked on an actor outside the registry — applies waiting-on:<actor> and posts the ### Waiting on comment so the steward ages it and the operator sees it in "Your open loops" (standard §14b). Use this whenever intake captures "X owes us an answer". |
--dod="item1|item2" |
no | Pipe-separated DoD items. Default: single item derived from title. |
--objective="..." |
no | Objective text. Defaults to the title. |
--context="..." |
no | Additional context beyond the source link. |
--state-news |
no | Flag: item is project-state news, not a task. Post a one-line comment on the epic (return EPIC:#NN), or append it to an internal project's log.md (return PROJECT:<slug>). |
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 · +1 lines 96dc58fc3428
- 7d ago Changed · +28 lines 4bb9814649ca
- 9d ago Changed · +18 lines 58e097ef3264
- 11d ago Changed · +23 lines · +22 tokens per session f8d06ff03e58
- 1mo ago First seen · 184 lines · 88 tokens per session scan A b4f88211db2a
project-intake is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 110 tokens to every session and 4,754 once invoked, about $0.0004 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-07.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…