Public work · Code and objects

Built to be opened.

Small utilities, reusable starting points, and physical designs from the workbench at One Thirteen.

Explore GitHub

Why it is public

Useful work gets better when people can see it.

These projects are intentionally small and practical. Open code makes them easier to learn from, adapt, question, and improve—and gives something back to the communities behind the tools we use every day.

01 · Repositories

Software and starting points.

All repositories ↗

Featured · Swift · macOS

Token

A focused menu bar utility for checking usage and spend across OpenAI, Anthropic, and OpenRouter administrative APIs.

02 · Printable objects

Beyond the screen.

One Thirteen on MakerWorld ↗

03 · Contributing

A useful change can be small.

Report a reproducible issue, clarify a confusing instruction, propose a focused improvement, or send a pull request. Each repository documents the contribution path that fits it best.

01

Find the project

Read its README, requirements, license, and current project status.

02

Start with context

Describe the problem, expected behavior, and a narrow proposed change.

03

Make it reviewable

Keep pull requests focused and include tests or examples where they help.

See the work

Clone it.
Change it.

Browse the repositories, open an issue, or use the contact form when you are not sure where a question belongs.