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 xuansenpa1/skillrevise --skill syzlang-ioctl-basicsgit clone --depth 1 https://github.com/xuansenpa1/skillreviseWrote 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/xuansenpa1/skillrevise/syzlang-ioctl-basics)<a href="https://agentmods.dev/skills/xuansenpa1/skillrevise/syzlang-ioctl-basics"><img src="https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/syzlang-ioctl-basics/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/xuansenpa1/skillrevise/syzlang-ioctl-basics"><img src="https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/syzlang-ioctl-basics.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.00021 | $0.00613 |
| Opus 5 | $0.00010 | $0.00307 |
| Sonnet 5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
syzlang-ioctl-basics 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 9d 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.
This is a copy
100% identical to syzlang-ioctl-basics — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Syzlang Ioctl Basics
Syzkaller's description language (syzlang) describes syscalls for fuzzing.
Description files are located at /opt/syzkaller/sys/linux/*.txt.
Syscall Syntax
Basic form:
syscall_name(arg1 type1, arg2 type2, ...) return_type
Specialized syscalls use $ suffix:
syscall$VARIANT(args...) return_type
Common Type Patterns
| Pattern | Meaning |
|---|---|
const[VALUE] |
Fixed constant value |
flags[flag_set, type] |
Bitfield from flag set |
ptr[direction, type] |
Pointer (in, out, inout) |
intptr[min:max] |
Integer pointer with range |
int8, int16, int32 |
Fixed-size integers |
int16be, int32be |
Big-endian integers |
array[type] |
Variable-length array |
array[type, count] |
Fixed-length array |
Ioctl Patterns
For ioctls with output:
ioctl$CMD(fd fd_type, cmd const[CMD], arg ptr[out, int32])
For ioctls with input:
ioctl$CMD(fd fd_type, cmd const[CMD], arg ptr[in, struct_type])
For simple value ioctls:
ioctl$CMD(fd fd_type, cmd const[CMD], arg intptr[0:1])
For ioctls using ifreq structure (from socket.txt):
ioctl$CMD(fd fd_type, cmd const[CMD], arg ptr[in, ifreq_t[flags[flag_set, int16]]])
Struct Definitions
Structs must have typed fields:
struct_name {
field1 type1
field2 type2
}
Flag Sets
Define reusable flag sets:
flag_set_name = FLAG1, FLAG2, FLAG3
Then use with flags[flag_set_name, int16].
Resources
File descriptor resources:
resource resource_name[fd]
Read/Write Syscalls
For specialized read/write:
read$suffix(fd fd_type, buf ptr[out, buffer_type], count len[buf])
write$suffix(fd fd_type, buf ptr[in, buffer_type], count len[buf])
Tips
- Check existing files for patterns (e.g.,
sys/linux/socket.txt) - Run
make descriptionsafter edits to validate syntax - Some constants only exist on certain architectures
- Use
ptr[in, ...]for input,ptr[out, ...]for output
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.
- 9d ago First seen · 98 lines · 21 tokens per session scan A f733ad59a34b
syzlang-ioctl-basics is a skill published in the GitHub repository xuansenpa1/skillrevise (56 stars, last pushed 7d ago), licensed MIT. It adds 21 tokens to every session and 613 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to syzlang-ioctl-basics, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…