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 Plazmodium/odin-workflow --skill graphqlgit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote 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/plazmodium/odin-workflow/graphql)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/graphql"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/graphql/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/plazmodium/odin-workflow/graphql"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/graphql.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.00032 | $0.02710 |
| Opus 5.5 | $0.00013 | $0.01084 |
| Sonnet 5.5 | $0.00006 | $0.00542 |
| Haiku 4.5 | $0.00003 | $0.00271 |
Grade A, and why
graphql 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.
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 — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GraphQL API Design
Instructions
- Assess the API need: Flexible queries, real-time data, or complex relationships.
- Follow GraphQL conventions:
- Schema-first or code-first approach
- Proper type definitions
- N+1 query prevention with DataLoader
- Input validation
- Provide complete examples: Include schema, resolvers, and client queries.
- Guide on best practices: Pagination, error handling, authentication.
Schema Design
Basic Types
type User {
id: ID!
email: String!
name: String!
avatar: String
role: Role!
posts: [Post!]!
createdAt: DateTime!
updatedAt: DateTime!
}
type Post {
id: ID!
title: String!
content: String!
published: Boolean!
author: User!
comments: [Comment!]!
tags: [Tag!]!
createdAt: DateTime!
}
enum Role {
USER
ADMIN
MODERATOR
}
scalar DateTime
Input Types
input CreateUserInput {
email: String!
name: String!
password: String!
role: Role = USER
}
input UpdateUserInput {
email: String
name: String
avatar: String
}
input PostFilters {
published: Boolean
authorId: ID
tags: [String!]
search: String
}
Queries and Mutations
type Query {
# Single resource
user(id: ID!): User
post(id: ID!): Post
# Collections with pagination
users(
first: Int
after: String
filter: UserFilter
): UserConnection!
posts(
first: Int
after: String
filter: PostFilters
orderBy: PostOrderBy
): PostConnection!
# Current user
me: User
}
type Mutation {
# User mutations
createUser(input: CreateUserInput!): CreateUserPayload!
updateUser(id: ID!, input: UpdateUserInput!): UpdateUserPayload!
deleteUser(id: ID!): DeleteUserPayload!
# Auth mutations
login(email: String!, password: String!): AuthPayload!
logout: Boolean!
# Post mutations
createPost(input: CreatePostInput!): Post!
updatePost(id: ID!, input: UpdatePostInput!): Post!
publishPost(id: ID!): Post!
deletePost(id: ID!): Boolean!
}
type Subscription {
postCreated: Post!
commentAdded(postId: ID!): Comment!
}
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.
- 1mo ago First seen · 549 lines · 32 tokens per session scan A 54366a7142f1
graphql is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 2,710 once invoked, about $0.0001 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-01.
Other skills, from other repositories
pipefy-api-fallback
Use this skill when a toolkit operation fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow…
nornweave-api
Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…
user-usecases
Database of real user use cases for APIbase platform. Contains detailed examples of how specific APIs are onboarded, wrapped, and served to AI agents. Use this skill when you need to reference real integration examples, explain the APIbase onboarding process, or design new API wrappers based on proven patterns.
tray-multicd
API de Multi-CD (Centros de Distribuição) da Tray. Cobre o CRUD de centros de distribuição (/multicd/distribution-centers: listar, consultar, criar, atualizar e excluir CDs) e a gestão de estoque distribuído por CD (/multicd/stock/detailed/product/:id, /multicd/stock/detailed/variant/:id e PUT…
tray-status-pedido
API de Status de Pedido da Tray (recurso /orders/statuses). Cobre o CRUD completo do CATÁLOGO de status de pedido da loja: listar, consultar por ID, criar, atualizar e excluir tipos de status, definindo nome, descrição, cores hexadecimais (backgroundcolor/fontcolor) e o tipo de fluxo (type: open/closed/cancelled).…
tray-autorizacao
Autenticação e autorização na API da Tray. Utilize quando o desenvolvedor precisar implementar o fluxo OAuth 2.0, gerar chaves de acesso (accesstoken), renovar tokens expirados via refreshtoken, ou tratar erros de autenticação na plataforma Tray. Inclui o fluxo completo de 3 etapas, campos de resposta, tempos de…