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 spree/agent-skills --skill spree-projectgit clone --depth 1 https://github.com/spree/agent-skillsWrote 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/spree/agent-skills/spree-project)<a href="https://agentmods.dev/skills/spree/agent-skills/spree-project"><img src="https://agentmods.dev/badge/skills/spree/agent-skills/spree-project.svg" alt="Measured on agentmods" 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.00080 | $0.02032 |
| Opus 5 | $0.00040 | $0.01016 |
| Sonnet 5 | $0.00016 | $0.00406 |
| Haiku 4.5 | $0.00008 | $0.00203 |
Grade A, and why
spree-project 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 7d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spree Commerce Project
A Rails application powered by Spree Commerce.
Project flavors — detect FIRST, it changes every command
Not every Spree app is a create-spree-app project. Check these signals in order before running anything:
| Signal | Flavor | How commands run |
|---|---|---|
backend/Gemfile mentions spree + docker-compose.yml at root |
create-spree-app project (5.4+) | spree <cmd> — the @spree/cli routes into the Docker web container |
Rails app at root (config/application.rb, Gemfile with spree) + docker-compose.yml with a Spree image/build |
spree-starter-style Docker app | spree <cmd> if the CLI resolves (npx spree --version); else docker compose exec web <cmd> |
| Rails app at root with spree gems, no Docker wiring | classic Rails app (typical pre-5.4) | Native, from the app root: bin/rails …, bundle exec rake … |
Command mapping — Spree CLI form → classic-app native form:
| Task | Spree CLI (Docker) | Classic Rails app |
|---|---|---|
| Boot for development | spree dev |
bin/dev (or bin/rails server) |
| Rails console | spree console |
bin/rails console |
| Install + run migrations | spree migrate |
bin/rake spree:install:migrations && bin/rails db:migrate |
| Version upgrade | spree upgrade |
bundle update <spree gems>, migrations, then bin/rake spree:upgrade |
| Run a generator | spree generate api_resource … |
bin/rails g spree:api_resource … (spell the spree: prefix yourself — auto-prefixing is a CLI feature) |
| Any rake task | spree rake <task> |
bundle exec rake <task> |
| Seeds / sample data | spree seed / spree sample-data |
bin/rails db:seed / bin/rails spree:load_sample_data |
| Arbitrary command | spree exec <cmd> |
just run <cmd> |
Other flavor differences:
- Rails root:
backend/in create-spree-app projects,.in classic apps. Paths written asbackend/app/…in these skills meanapp/…on a classic app. - Local docs (
node_modules/@spree/docs/dist/) exist only when the project installs@spree/docs. On classic apps, use https://spreecommerce.org/docs/llms.txt instead. - The rake tasks themselves (
spree:install:migrations,spree:upgrade, thespree:model/spree:api_resourcegenerators) ship inside the spree gems and work identically in both flavors — only the invocation wrapper differs. Notespree:upgradeand the generators ship in spree_core 5.5+: a pre-5.5 app gains them after thebundle updatestep of the upgrade, so on old apps run the gem bump first.
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.
- 7d ago First seen · 129 lines · 80 tokens per session scan A 2303251e4128
spree-project is a skill published in the GitHub repository spree/agent-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 2,032 once invoked, about $0.0004 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-31.
Other skills, from other repositories
new
Create a new project to start development quickly.
rspec-conventions
Rootstrap RSpec conventions. Use when writing, reviewing, or editing RSpec test files (spec//spec.rb, spec/railshelper.rb, spec/spechelper.rb, spec/support//.rb) or factories. Covers describe/context structure, let/subject, matchers, factories, mocking/stubbing, shared examples, and spec types (model, request…
ruby-patterns
Ruby/Rails: blocks, metaprogramming, ActiveRecord, Sidekiq, RSpec, Sorbet, Hanami. Triggers: Ruby, Rails, ActiveRecord, Sidekiq, RSpec, Gemfile, bundler, Hanami, Sorbet.
ruby-rules
Ruby coding rules: style, patterns, security, testing. Triggers: .rb, Gemfile, .gemspec, Rails, ActiveRecord, Sidekiq, RSpec, Sorbet, rubocop.
ruby-expert
Expert-level Ruby development with Rails, modern features, testing, and best practices. Use when the user mentions Ruby on Rails, RSpec, gem, Sinatra, or metaprogramming, or when the task involves Ruby 3+ Features, Object-Oriented, Functional Features, or Pattern Matching.
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…