using-celery

using-celery is a skill for Claude Code from FortiumPartners/ensemble. It costs 45 tokens per session (2,952 once invoked), scanned A, original, MIT.

A development reference for Celery, a Python system that runs background jobs outside the main request, with Beat for scheduled jobs. It also covers Redis or RabbitMQ message brokers and FastAPI integration.

In plain words
What is it for?
It is for building background jobs, periodic tasks, task workflows, and asynchronous processing in Python applications.
Why use it?
It helps keep slow, asynchronous, or recurring work out of the main application flow and provides patterns for connecting these parts safely.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ensemble-development plugin — 11 skills, 7 agents shipped together

Good fit It is for building background jobs, periodic tasks, task workflows, and asynchronous processing in Python applications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fortiumpartners/ensemble/using-celery
Install

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.

Any agent
npx skills add FortiumPartners/ensemble --skill using-celery
Clone the repo
git clone --depth 1 https://github.com/FortiumPartners/ensemble

Made for: Claude Code.

Or install ensemble-development, the plugin that ships this one along with the rest of its 11 skills, 7 agents.

Wrote 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.

agentmods badge for using-celery

README.md
[![agentmods](https://agentmods.dev/badge/skills/fortiumpartners/ensemble/using-celery/github.svg)](https://agentmods.dev/skills/fortiumpartners/ensemble/using-celery)
Your own site
<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/using-celery"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/using-celery/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.

agentmods 80×15 button for using-celery

Your own site · 80×15
<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/using-celery"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/using-celery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,952 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.02952
Opus 5.5 $0.00018 $0.01181
Sonnet 5.5 $0.00009 $0.00590
Haiku 4.5 $0.00005 $0.00295

Measured 1mo ago against content hash 4814bfa96b29, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

using-celery 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 1mo ago.

The scan reads SKILL.md. This mod also ships 6 executable files (examples/fastapi_celery.example.py, examples/task_patterns.example.py, templates/beat_schedule.template.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

packages/development/skills/using-celery/SKILL.md · 457 lines

How it starts

The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Celery & Beat Development Skill

Quick Reference

Celery 5.3+ distributed task queue with Beat scheduler for Python applications. Background job processing, periodic scheduling, workflow patterns, and FastAPI integration.


Table of Contents

  1. Quick Reference
  2. When to Use
  3. Project Structure
  4. Celery Application Setup
  5. Task Definitions
  6. Queue Routing
  7. Beat Scheduler
  8. Workflow Patterns
  9. FastAPI Integration
  10. Testing
  11. CLI Commands
  12. Essential Configuration
  13. Anti-Patterns to Avoid
  14. Integration Checklist
  15. See Also

When to Use

This skill is loaded by backend-developer when:

  • celery or celery[redis] in dependencies
  • celeryconfig.py or celery.py present
  • Beat schedule configuration detected
  • User mentions "background tasks", "job queue", or "periodic tasks"
  • Task decorator patterns (@app.task) found

Minimum Detection Confidence: 0.8 (80%)

Prerequisite: Python skill should be loaded for core patterns.


Project Structure

my_project/
├── src/my_app/
│   ├── celery_app.py        # Celery application
│   ├── config.py            # Settings
│   ├── tasks/               # Task modules
│   │   ├── email.py
│   │   ├── reports.py
│   │   └── cleanup.py
│   └── workers/queues.py    # Queue definitions
├── tests/
│   ├── conftest.py          # Celery fixtures
│   └── tasks/
├── docker-compose.yml       # Redis + workers
└── pyproject.toml

Celery Application Setup

from celery import Celery
from kombu import Queue
from .config import settings

app = Celery(
    "my_app",
    broker=settings.celery_broker_url,
    backend=settings.celery_result_backend,
    include=["my_app.tasks.email", "my_app.tasks.reports"],
)

app.conf.update(
    task_serializer="json",
    accept_content=["json"],
    result_serializer="json",
    timezone="UTC",
    enable_utc=True,
    task_track_started=True,
    task_time_limit=300,
    task_soft_time_limit=240,
    worker_prefetch_multiplier=1,
    task_acks_late=True,
    task_reject_on_worker_lost=True,
)

# Queue routing
app.conf.task_queues = (
    Queue("default", routing_key="default"),
    Queue("high_priority", routing_key="high"),
    Queue("low_priority", routing_key="low"),
)

Read the full file on GitHub · 457 lines

Changes

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.

  1. 1mo ago First seen · 457 lines · 45 tokens per session scan A 4814bfa96b29

Subscribe to this mod's changes

using-celery is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 2,952 once invoked, about $0.0002 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-03.

Related

Other skills, from other repositories

nodejs

Use when building or operating a plain Node.js / Express 5 backend service: project layout, async correctness, central error middleware, fail-fast config, graceful shutdown on SIGTERM. NOT DI modules/providers/guards (that is nestjs), NOT the type system or tsconfig (that is typescript), NOT REST contract design (that…

ericrisco/rsc-harness · 77 tokens

api-contract-audit

Static OpenAPI contract audit - endpoint drift (spec vs code), schema drift, status-code mismatch, breaking-change detection vs previous spec version, versioning consistency, security scheme alignment, deprecation markers, Richardson Maturity L0-L3 scoring. Framework auto-gen for FastAPI, NestJS…

marcoguillermaz/Tierward · 78 tokens

api-design

API design audit: endpoint naming, HTTP verbs, response shapes, error codes, pagination, validation consistency. Run when adding or modifying API routes.

marcoguillermaz/Tierward · 0 tokens

cli-forge-lld

Generate a Low-Level Design (LLD) document for a software component or service. Use when the user mentions 'LLD', 'low-level design', 'detailed design', 'class diagram', 'sequence diagram', 'API spec', 'database schema', 'component design', 'module design', 'STRIDE', 'threat model', or asks for detailed technical…

Destynova2/cli-code-skills · 133 tokens

agentmail

Give AI agents their own email inboxes using the AgentMail API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, handling attachments, organizing with labels, creating drafts for human approval, or setting up real-time notifications via webhooks/websockets. Supports…

AgentComputerAI/torch · 69 tokens

architecture-patterns

Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…

yonatangross/orchestkit · 56 tokens