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 agentmods add commands/rhyanvargas/agentic-development-starter-kit/quick-startgit clone --depth 1 https://github.com/rhyanvargas/agentic-development-starter-kitWhat 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 | $0.00000 | $0.00244 |
| Opus 5 | $0.00000 | $0.00122 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
quick-start 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 2d 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.
What it actually says
/quick-start
Initialize the ADSK spec-driven workflow for a project.
Skill
Read and follow skills/spec-driven-workflow, especially references/getting-started.md.
Usage
/quick-start
Behavior
- Detect stack (package managers, frameworks, test/lint tools).
- Detect artifact homes (Cursor
.cursor/...vs portabledocs/...) viareferences/artifact-homes.md; when Cursor wiring is present, update or propose.cursor/rules/project/andproject-cmdswith real verify commands. - Confirm ADSK skills are discoverable under
.agents/skills/. If missing, point todocs/using-adsk.md(npx skills add rhyanvargas/agentic-development-starter-kit). - End with a short where truth lives checklist (all four required):
- Spec/plan artifact home (resolved path)
- Verify commands location (
project-cmdsor portable equivalent) - Skills discovery path (
.agents/skills/) - Next command: greenfield →
/draft-spec; brownfield →/extract-spec
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.
- 2d ago First seen · 25 lines · 0 tokens per session scan A 9ecbeb30e2c9
quick-start is a command published in the GitHub repository rhyanvargas/agentic-development-starter-kit (2 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 244 tokens. 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.