AI Notes

Created: 2025-01-26 16:21:36 | Last updated: 2025-05-27 23:36:12 | Status: Public


jailbreaks for models

https://github.com/elder-plinius/L1B3RT4S/blob/main/ALIBABA.mkd


People are not giving any real arguments for why is it better to use API instead of Web. I was burning over 400$ a month in API, and i use WEB as much as i can because if i worked on large files like 700-1000 lines of code, i would burn 20$ of api in few hours.

What kind of argument is that you pay what you use. Claude WEB allows you not care about size of your files, 20$ for claude is a great deal. If you know how to use Claude web, then you wont hit limits as much.

Ill give you 2 gamechanging tips.

If you want to use API, buy 10$ subscription for github copilot, install cline in VSC, set cline to suck AI from VSC extension, in this case Copilot, and use sonnet 3.5 for flat 10$. It will sometimes show you rate limit exceeded, but when it does, just wait a bit and try again. in the lat few days ive used it so much i would pay 45$ for api itself if i used it directly, but instead i only paid 10$ (Before i knew that trick i was burning 400$ a month). You can try this solution via free version of copilot (monthly limits).

Second tip for web usage. Basically claude's limits work in 5h spans. And it counts from the first message you write. So lets say you write your first message at 5pm, this means new limit will be aavailable at 10pm, no matter if you use whole limit or not.

So the trick is to force it to reset on hours that we want. Right now im messaging it via iphone automations at 7:01 am, to force it to reset my limit at 12pm. If you know that you mostly work in claude at 5-7 pm, then just message it “hi” at 1pm this way you can use all your limit from 5-6pm, it will reset on 6pm, and you have fresh batch of limit at 6:01, voi la.


Make it into a custom style.

Reset claude to june 2024

You have to explicitly tell it to not use bullets AND to favor fully developed sentences and paragraphs. Within that framework you can further specify if you want it to have a more or less verbose style.


So you can say like, “$ cat myfile.txt|claude ‘remove the duplicated newlnies’”


(in this case I have ‘claude’ aliased to a custom script that sends STDIN to claude and gives me the output, and it works wonderfully)


“I want a Python script that changes all pixels with [hex value] to [new hex value] in all .png files whose filenames contain [string] for that folder and subfolders”.


https://github.com/sigoden/aichat ?

Having an llm in the terminal helping with scripting and complex bash commands changed my life


“You’re an esteemed professor of astrophysics at Harvard University. You’re given a research article to read and summarise. Take a deep breath and think deeply about it!

You’re particularly good at identifying the key results and why they’re significant. While you can use your general knowledge about astronomy and astrophysics, you should only include content from the paper you’re given in your summary.

For your summary, use the structure from “paper-summary-template.md” in the project knowledge.

Use level 1 (#) headings for the title
Use level 2 (##) headings for main sections 
Use bold for key terms on first mention
Use italics for emphasis and paper names

Start with the paper title as a heading then the full author list below. Authors are listed by their surname and initials with a period, comma separated.

If you can figure it out, then add a web link to the paper. Title the link “Link”.

Then give a concise bullet point summary of the paper’s key ideas and important results - call this section “Key Ideas”.

Then summarise each major section of the paper, using the these exact headings: Introduction, Data, Method, Results, Discussion, Weaknesses, Conclusions, Future Work. Use 1 to 3 concise bullets per section. Bullets should be full sentences. You can use sub-bullets if necessary.

After summarising each section, provide a section titled “Tags” with a hashtag list separated by spaces. There will be 2 subsections of hashtags. Don’t include a heading for each subsection but do seperate the hashtag groups with a new line.

The first subsection of hashtags should list hashtags for all the telescopes, surveys, datasets, models, simulations, and codes that can be found in the method and results sections of the paper. Furthermore, only include those that are proper nouns.

Right below this, the second subsection of hashtags should describe the key science areas of the paper. For this subsection, ONLY use hashtags from the list I’ve given in the file “astronomy-keywords.txt” in the project knowledge. First, knowing the astronomy subfield the paper is about, identify the most relevant tag groups from the list. Then from these groups find the most relevant hashtags.

The next section should be titled “Glossary” with a glossary of terms used in the paper, in the format of a table.

Use markdown. Use latex for any math. You speak in UK English. You write in clear technical language.

Each section of your summary should have a markdown heading. Make it look nice and use bold and italics where necessary. Start straight with the paper title; nothing before that.

EVERY bullet should include a footnote listed right at the end of the summary in a section titled “References” with the exact text of the most relevant quote from the paper (use full sentences, put in quotes), and the section and page number in the paper where it can be found.”


“write a .bat file with our py file inside of it, including checks for dependencies, streamlined so all I have to do is save and right click .bat -> Run as admin”


bro use scipdf parser


Just fyi there is a python library called ‘markitdown’ that converts pretty much anything (including PDFs) into markdown. It’s made by Microsoft, and works very well.

https://old.reddit.com/r/LocalLLaMA/comments/1hfdx7k/github_microsoftmarkitdown_python_tool_for/


I had a variety of bash scripts I use to do any number of things to images:

optimize svg
optimize png
convert to webp
resize image

I wrote most of those by hand, following man pages, and collecting the occasional snippet I found online.

I used Claude a few months ago to add some more features to my scripts and use Gum https://github.com/charmbracelet/gum

Now instead of trying to remember which function to call in the terminal, I have them all under one function (img), and it’s all colorized and nearly arranged with more options, depending which one I choose.