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 jxoesneon/Ciel --skill everything-claude-code-conventionsgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/everything-claude-code-conventions)<a href="https://agentmods.dev/skills/jxoesneon/ciel/everything-claude-code-conventions"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/everything-claude-code-conventions.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.00021 | $0.00650 |
| Opus 5 | $0.00010 | $0.00325 |
| Sonnet 5 | $0.00004 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
everything-claude-code-conventions 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 4d 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
CIEL ADAPTATION: Everything-Claude-Code-Conventions (The Conventions Layer)
This skill provides the "Conventions Layer" for the CIEL framework, ensuring that all generated code, commits, and project structures adhere to established standards. It is the stylistic "Source of Truth" for CIEL's engineering output.
Integration Context
Adapted from ~/.agents/skills/everything-claude-code-conventions/. This skill provides the granular rules used by the Auditor sub-agent in the do (Execution) phase and the Verification-Loop (Finality).
Core Standards
1. Linguistic & Naming
- Files/Functions:
camelCase - Classes:
PascalCase - Constants:
SCREAMING_SNAKE_CASE - Imports: Relative imports are preferred.
2. Commit Protocol
CIEL MUST use Conventional Commits:
feat: New featuresfix: Bug fixestest: Adding or updating testsdocs: Documentation changeschore: Maintenance tasks- Mood: Use imperative mood ("Add", "Fix", "Update").
3. Orchestration Logic
- Discovery: During Phase 0 of a plan, CIEL must re-verify these conventions against the current repo state (e.g., checking
package.jsonand.prettierrc). - Audit: The Auditor sub-agent MUST flag any implementation that deviates from these naming or structural patterns.
- Persistence: All successful conventions must be indexed in MemPalace as
EngineeringStandardnodes.
Standard Workflows
1. Adding a New Skill
- Create
skills/{skill-name}/SKILL.md. - Add adaptation metadata if applicable.
- Index in MemPalace.
2. Addressing Review Feedback
- Explicitly cite the feedback in the commit message.
- Update the relevant skill/agent/code to resolve the discrepancy.
- Re-run the verification-loop.
Original Architecture and Error Handling patterns preserved at source.
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.
- 4d ago First seen · 77 lines · 21 tokens per session scan A 0499ef960d94
everything-claude-code-conventions is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 7d ago), licensed Apache-2.0. It adds 21 tokens to every session and 650 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
codex-review
Professional code review with auto CHANGELOG generation, integrated with Codex AI.
vanellus
Skill "vanellus" from markmhendrickson/ateles, covering vanellus — pr steward, identity, principals, core job and automated pr review (swarm-panel invocation).
dedup
Dedupe-only pass for BASESHA..HEAD: remove duplicate code introduced by the diff or reuse existing shared utils; applies changes + commits.
plan-critique-loop
Critique and revise an existing plan doc up to 3 iterations, using accept/reject triage and stopping early when no important feedback remains. Use when refining a plan/.md before implementation.